Providing enhanced functionality in an interactive electronic technical manual

ABSTRACT

Embodiments of the present disclosure provide methods, apparatus, systems, computer program products for generating an annotation for textual information and/or media content for technical documentation for an item in an interactive electronic technical manual system (IETM) configured to provide electronic and credentialed access to the technical documentation via an IETM viewer. In one embodiment, a method is provided comprising: providing a window for display comprising the textual information and/or media content; receiving input of a selection of an annotation selection mechanism; and responsive to receiving the input: generating the annotation for the textual information and/or media content; receiving an indication of a position in the textual information and/or media content to associate with the annotation; and providing an annotation window for the annotation for display via the IETM viewer, wherein the annotation window comprises an attach file mechanism, a capture mechanism, a share mechanism, and a change form mechanism.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 17/029,311 filed Sep. 23, 2020, which is a continuation of Ser.No. 17/026,636, filed Sep. 21, 2020, the contents of which areincorporated by reference in their entirety into the presentapplication.

TECHNOLOGICAL FIELD

Embodiments of the present disclosure generally relate to providingenhanced functionality in an interactive electronic technical manual(IETM). The inventors have developed solutions that increase theefficiency, functionality, speed, capabilities, and user friendlinessover conventional IETMs.

BACKGROUND

IETMs and other technical data generally hold large amounts ofinformation that can include multiple volumes and hundreds or thousandsof data modules when in electronic format. When users of IETMs, or othertechnical data that are provided electronically, need to look for aspecific subject, they need to go over a lengthy electronic table ofcontents, similar to a paper book, but using links, which can includenested subsystems (and sub-subsystems) within systems. This requires theusers to know not only the exact nomenclature of the item they seek(many times this is unknown), but how to navigate through the seeminglyendless array of nested data. This results in a lot of time spent byusers, trying to look in many different places (and sometimes, out ofexasperation, just look from A to Z) to find the information, whichresults in inefficiency, loss of time, and waste of expensive resources.

Furthermore, although many conventional IETMs provide some type ofinteractive functionality with respect to the technical data that allowusers to interactively view the data, such functionality is typicallylimited to capabilities and do not address many of the technical issuesencountered when providing an electronic interface for a large amount ofinformation, as well as technical improvements that provide featuresbeyond just simply allowing the user to view such information. Forexample, the technical data may involve information that is highlyconfidential such as information on military equipment. Manyconventional IETMs fail to provide functionality to control secureaccess to the technical data, as well as control user functionalitywithin the IETMs in viewing and using the technical data in a securemanner.

Thus, a need exists in the industry to address technical problemsrelated to efficiently providing technical data to users in auser-friendly manner. Further, a need exists in the industry to providetechnical improvements to allow for enhanced functionality with respectto the technical data. It is with respect to these considerations andothers that the disclosure herein is presented.

BRIEF SUMMARY

Embodiments of the present disclosure provide methods, apparatus,systems, computer program products and/or the like for generating anannotation for at least one of textual information and media content fortechnical documentation for an item in an interactive electronictechnical manual system (IETM) configured to provide electronic andcredentialed access to the technical documentation for the item via anIETM viewer. In accordance with one aspect of the present disclosure, amethod for generating an annotation for at least one of textualinformation and media content for technical documentation for an item inan interactive electronic technical manual system (IETM) configured toprovide electronic and credentialed access to the technicaldocumentation for the item via an IETM viewer is provided. In variousembodiments, the method comprises: providing a window for display viathe IETM viewer executing on a user computing entity being used by auser signed into the IETM, the window comprising at least one of thetextual information and the media content; receiving input of aselection of an annotation selection mechanism provided on the window,wherein the selection of the annotation selection mechanism is performedby the user via the IETM viewer; and responsive to receiving the inputof the selection of the annotation selection mechanism: generating theannotation for the at least one of the textual information and the mediacontent; receiving an indication of a position in at least one of thetextual information and the media content to associate with theannotation; providing an annotation window for the annotation fordisplay via the IETM viewer, wherein the annotation window comprises anattach file mechanism, a capture mechanism, a share mechanism, and achange form mechanism; receiving input of a selection of the attach filemechanism, wherein the selection of the attach file mechanism isperformed by the user via the IETM viewer; responsive to receiving theinput of the selection of the attach file mechanism, facilitatingattaching a file to the annotation; receiving input of a selection ofthe capture mechanism, wherein the selection of the capture mechanism isperformed by the user via the IETM viewer; responsive to receiving theinput of the selection of the capture mechanism: capturing an image ofthe window; and attaching the image to the annotation; receiving inputof a selection of the share mechanism, wherein the selection of theshare mechanism is performed by the user via the IETM viewer; responsiveto receiving the input of the selection of the share mechanism,configuring the annotation so that other user can view the annotation;receiving input of a selection of the change form mechanism, wherein theselection of the change form mechanism is performed by the user via theIETM viewer; and responsive to receiving the input of the selection ofthe change form mechanism: providing a change form for display via theIETM viewer; pre-populating at least one field on the change form basedat least in part on information found in the annotation; and submittinga request for change to at least one of the textual information and themedia content based at least in part on information provided on thechange form.

In accordance with another aspect of the present disclosure, anapparatus is provided. In various embodiments, the apparatus comprisesat least one processor and at least one memory comprising computerprogram code. The at least memory and the program code are configuredto, with the at least one processor, cause the apparatus to: provide awindow for display via the IETM viewer executing on a user computingentity being used by a user signed into the IETM, the window comprisingat least one of the textual information and the media content; receiveinput of a selection of an annotation selection mechanism provided onthe window, wherein the selection of the annotation selection mechanismis performed by the user via the IETM viewer; and responsive toreceiving the input of the selection of the annotation selectionmechanism: generate the annotation for the at least one of the textualinformation and the media content; receive an indication of a positionin at least one of the textual information and the media content toassociate with the annotation; provide an annotation window for theannotation for display via the IETM viewer, wherein the annotationwindow comprises an attach file mechanism, a capture mechanism, a sharemechanism, and a change form mechanism; receive input of a selection ofthe attach file mechanism, wherein the selection of the attach filemechanism is performed by the user via the IETM viewer; responsive toreceiving the input of the selection of the attach file mechanism,facilitate attaching a file to the annotation; receive input of aselection of the capture mechanism, wherein the selection of the capturemechanism is performed by the user via the IETM viewer; responsive toreceiving the input of the selection of the capture mechanism: capturean image of the window; and attach the image to the annotation; receiveinput of a selection of the share mechanism, wherein the selection ofthe share mechanism is performed by the user via the IETM viewer;responsive to receiving the input of the selection of the sharemechanism, configure the annotation so that other user can view theannotation; receive input of a selection of the change form mechanism,wherein the selection of the change form mechanism is performed by theuser via the IETM viewer; and responsive to receiving the input of theselection of the change form mechanism: provide a change form fordisplay via the IETM viewer; pre-populate at least one field on thechange form based at least in part on information found in theannotation; and submit a request for change to at least one of thetextual information and the media content based at least in part oninformation provided on the change form.

In accordance with yet another aspect of the present disclosure, anon-transitory computer storage medium is provided. In variousembodiments, the non-transitory computer storage medium comprisesinstructions stored thereon. The instructions being configured to causeone or more processors to at least perform operations configured to:provide a window for display via the IETM viewer executing on a usercomputing entity being used by a user signed into the IETM, the windowcomprising at least one of the textual information and the mediacontent; receive input of a selection of an annotation selectionmechanism provided on the window, wherein the selection of theannotation selection mechanism is performed by the user via the IETMviewer; and responsive to receiving the input of the selection of theannotation selection mechanism: generate the annotation for the at leastone of the textual information and the media content; receive anindication of a position in at least one of the textual information andthe media content to associate with the annotation; provide anannotation window for the annotation for display via the IETM viewer,wherein the annotation window comprises an attach file mechanism, acapture mechanism, a share mechanism, and a change form mechanism;receive input of a selection of the attach file mechanism, wherein theselection of the attach file mechanism is performed by the user via theIETM viewer; responsive to receiving the input of the selection of theattach file mechanism, facilitate attaching a file to the annotation;receive input of a selection of the capture mechanism, wherein theselection of the capture mechanism is performed by the user via the IETMviewer; responsive to receiving the input of the selection of thecapture mechanism: capture an image of the window; and attach the imageto the annotation; receive input of a selection of the share mechanism,wherein the selection of the share mechanism is performed by the uservia the IETM viewer; responsive to receiving the input of the selectionof the share mechanism, configure the annotation so that other user canview the annotation; receive input of a selection of the change formmechanism, wherein the selection of the change form mechanism isperformed by the user via the IETM viewer; and responsive to receivingthe input of the selection of the change form mechanism: provide achange form for display via the IETM viewer; pre-populate at least onefield on the change form based at least in part on information found inthe annotation; and submit a request for change to at least one of thetextual information and the media content based at least in part oninformation provided on the change form.

In some embodiments, the annotation window further comprises a freeformfield configured to allow the user to enter a comment recorded for theannotation. In addition, in some embodiments, a date and a time when theannotation was generated is recorded along with the annotation. Further,in some embodiments, at least one of the file and the image is attachedto the request for change in response to receiving the input of theselection of the change form mechanism. Furthermore, in someembodiments, responsive to receiving the input of the selection of theshare mechanism and another user requesting to view the annotation, theannotation window including the information found in the annotation anda comments mechanism for the another user for display is provided,wherein the comments mechanism is configured to allow the another userto enter a comment to attach to the annotation. Finally, in someembodiments, input is received of a selection of a mechanism to view alist of annotations performed by the user via the IETM viewer.Responsive to receiving the selection of the mechanism to view the listof annotations, a list of annotations window including the list ofannotations including the annotation for at least one of the textualinformation and the media content is generated and provided for displayvia the IETM viewer, wherein the list of annotations includesannotations created by the user and annotations shared by other users,and the list of annotations window is configured to allow the user toselect an annotation found in the list of annotations to view.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the disclosure in general terms, reference willnow be made to the accompanying drawings, which are not necessarilydrawn to scale, and wherein:

FIG. 1 is a diagram of a system architecture that can be used inconjunction with various embodiments of the present disclosure;

FIG. 2 is a schematic of a management computing entity that may be usedin conjunction with various embodiments of the present disclosure;

FIG. 3 is a schematic of a user computing entity that may be used inconjunction with various embodiments of the present disclosure;

FIG. 4 is a process flow for signing in a user to an IETM in accordancewith various embodiments of the present disclosure;

FIGS. 5A and 5B provide examples of a sign-in window that may be used inaccordance with various embodiments of the present disclosure;

FIGS. 5C and 5D provide an example of a user's history report that maybe used in accordance with various embodiments of the presentdisclosure;

FIG. 6 is a process flow for viewing and interacting with a table ofcontents provided by an IETM in accordance with various embodiments ofthe present disclosure;

FIG. 7 provides an example of a window displaying a table of contents inaccordance with various embodiments of the present disclosure;

FIG. 8 is a process flow for filtering a table of contents in accordancewith various embodiments of the present disclosure;

FIG. 9 provides an example of a window displaying a table of contentsthat has been filtered in accordance with various embodiments of thepresent disclosure;

FIG. 10 is a process flow for tagging content with formatting found in asource of the content in accordance with various embodiments of thepresent disclosure;

FIG. 11 is a process flow for formatting content based at least in parton a format structure found in a source of the content in accordancewith various embodiments of the present disclosure;

FIG. 12A provides an example of a table of contents formatted accordingto S1000D standards;

FIG. 12B provides an example of a table of contents formatted accordingto a format structure found in one or more sources of the contents;

FIG. 12C provides an example of content from a source formattedaccording to a format structure found in the source;

FIG. 13 is a process flow for searching a table of contents inaccordance with various embodiments of the present disclosure;

FIG. 14 is a process flow for providing one or more predictions based atleast in part on search term(s) in accordance with various embodimentsof the present disclosure;

FIGS. 15A and 15B provide examples of a search window in accordance withvarious embodiments of the present disclosure;

FIG. 16 is a process flow for generating a list of parts in accordancewith various embodiments of the present disclosure;

FIG. 17 is a process flow for displaying a list of parts in accordancewith various embodiments of the present disclosure;

FIG. 18A provides an example of a window displaying a list of parts inaccordance with various embodiments of the present disclosure;

FIG. 18B provides an example of a mechanism for identifying levels forrelisting a list of parts in accordance with various embodiments of thepresent disclosure;

FIG. 18C provides an example of a preview displaying information for asupplier in accordance with various embodiments of the presentdisclosure;

FIG. 18D provides an example of a preview displaying a list of otheritems that use a part in accordance with various embodiments of thepresent disclosure;

FIG. 19 is a process flow for allowing a user to order a part via anIETM in accordance with various embodiments of the present disclosure;

FIG. 20 is a process flow for submitting an order for a part via an IETMin accordance with various embodiments of the present disclosure;

FIG. 21A provides an example of a window in which an option to order apart is provided in accordance with various embodiments of the presentdisclosure;

FIG. 21B provides an example of an electronic order form that can beused to order a part in accordance with various embodiments of thepresent disclosure;

FIG. 21C provides an example of a graphical code that can be scanned toorder a part in accordance with various embodiments of the presentdisclosure;

FIG. 22 is a process flow for displaying content for a topic found intechnical documentation for an item in accordance with variousembodiments of the present disclosure;

FIG. 23 is a process flow for causing parts found in textual informationto be displayed as selectable in accordance with various embodiments ofthe present disclosure;

FIG. 24 is a process flow for causing applicability found in textualinformation to be displayed as selectable in accordance with variousembodiments of the present disclosure;

FIG. 25 is a process flow for locked content in accordance with variousembodiments of the present disclosure;

FIG. 26 is a process flow for setting a security classification forspecific content in accordance with various embodiments of the presentdisclosure;

FIG. 27 provides an example of security classification formatting andfunctionality set for the display of content in accordance with variousembodiments of the present disclosure;

FIGS. 28A and 28B is a process flow for invoking functionality providedfor a topic in accordance with various embodiments of the presentdisclosure;

FIG. 29 is a process flow for displaying related information for a partin accordance with various embodiments of the present disclosure;

FIG. 30 provides an example of related information displayed for a partin accordance with various embodiments of the present disclosure;

FIG. 31 is a process flow for displaying information on the meaning ofan occurrence of applicability in accordance with various embodiments ofthe present disclosure;

FIG. 32 provides an example of displaying information on the meaning ofan occurrence of applicability in accordance with various embodiments ofthe present disclosure;

FIG. 33 is a process flow for displaying a data source for a topic inaccordance with various embodiments of the present disclosure;

FIG. 34A provides an example of a section of a data source displayed inaccordance with various embodiments of the present disclosure;

FIG. 34B provides an example of an entire data source displayed inaccordance with various embodiments of the present disclosure;

FIG. 35 is a process flow for generating an annotation in accordancewith various embodiments of the present disclosure;

FIG. 36A provides an example of a generated annotation in accordancewith various embodiments of the present disclosure;

FIG. 36B provides an example a change request form in accordance withvarious embodiments of the present disclosure;

FIG. 36C provides an example of a selection mechanism to generate anannotation in accordance with various embodiments of the presentdisclosure;

FIG. 36D provides an example of a report of change requests submitted bya user in accordance with various embodiments of the present disclosure;

FIG. 36E provides an example of a list of annotations generated by auser in accordance with various embodiments of the present disclosure;

FIG. 37 is a process flow for checking the steps found in a sequence inaccordance with various embodiments of the present disclosure;

FIG. 38 provides an example of sequential information in which stepsthat have been skipped are displayed as highlighted in accordance withvarious embodiments of the present disclosure;

FIG. 39 is a process flow for unlocking content as a result of a useracknowledging an alert in accordance with various embodiments of thepresent disclosure;

FIG. 40A provides an example of a portion of content that has beenlocked in accordance with various embodiments of the present disclosure;

FIG. 40B provides an example of a portion of content that has beenunlocked in accordance with various embodiments of the presentdisclosure;

FIG. 41 is a process flow for facilitating a user transferring a job inaccordance with various embodiments of the present disclosure;

FIG. 42 is a process flow for facilitating a user resuming a suspendedjob in accordance with various embodiments of the present disclosure;

FIG. 43A is an example of a mechanism to enable a user to transfer orresume a job in accordance with various embodiments of the presentdisclosure;

FIG. 43B is an example of a job transfer window in accordance withvarious embodiments of the present disclosure;

FIG. 43C is an example of a procedure that has been suspended inaccordance with various embodiments of the present disclosure;

FIG. 43D is an example of a procedure that has been resumed inaccordance with various embodiments of the present disclosure;

FIG. 44 is a process flow for causing media content that is displayed tobe updated based at least in part on a user scrolling through textualinformation in accordance with various embodiments of the presentdisclosure;

FIG. 45 provides an example of media content being updated as a userscrolls through textual information in accordance with variousembodiments of the present disclosure;

FIG. 46 is a process flow for causing display of a unit as highlightedin media content or referenced in textual information in accordance withvarious embodiments of the present disclosure;

FIG. 47A provides an example of a unit highlighted in an illustration inaccordance with various embodiments of the present disclosure;

FIG. 47B provides an example of units highlighted in textual informationin accordance with various embodiments of the present disclosure;

FIG. 48 is a process flow for providing functionality when a userreaches the end of content for a topic in accordance with variousembodiments of the present disclosure;

FIG. 49A provides an example of an end of topic mechanism in accordancewith various embodiments of the present disclosure;

FIG. 49B provides an example of a table of contents displayed as aresult of invoking end of module functionality in accordance withvarious embodiments of the present disclosure;

FIG. 50 is a process flow for providing functionality for wiring data inaccordance with various embodiments of the present disclosure;

FIG. 51A provides an example of an electrical schematic displayed inaccordance with various embodiments of the present disclosure;

FIG. 51B provides an example of a preview of a connector in accordancewith various embodiments of the present disclosure;

FIG. 51C provides an example of a list of components displayed in anelectrical schematic in accordance with various embodiments of thepresent disclosure;

FIG. 51D provides an example of a list of other electrical schematicsthat display a selected component in accordance with various embodimentsof the present disclosure;

FIG. 52 is a process flow for providing live wire functionality for aselected wire in accordance with various embodiments of the presentdisclosure;

FIG. 53 is an example of a wire diagram in accordance with variousembodiments of the present disclosure;

FIG. 54 is a process flow for providing crosshairs on a graph inaccordance with various embodiments of the present disclosure;

FIG. 55 is an example of crosshairs placed on a graph in accordance withvarious embodiments of the present disclosure;

FIG. 56 is a process flow for providing functionality for media contentinvolving 3D graphics in accordance with various embodiments of thepresent disclosure;

FIGS. 57A-D provide examples of a table of parts and a 3D graphicdisplayed in accordance with various embodiments of the presentdisclosure;

FIGS. 57E and 57F provide examples of a part removed from a 3D graphicin accordance with various embodiments of the present disclosure;

FIGS. 57G and 57H provide examples of a part solely displayed in a 3Dgraphic in accordance with various embodiments of the presentdisclosure;

FIG. 57I provides an example of axes on a 3D graphic displayed inaccordance with various embodiments of the present disclosure;

FIG. 58 is a process flow for providing components in media content asidentified in a hierarchy in accordance with various embodiments of thepresent disclosure;

FIG. 59A provides an example of a hierarchy of components displayed forcomponents found in media content in accordance with various embodimentsof the present disclosure;

FIG. 59B provides an example of a report displayed of componentsillustrated in media content but not listed in accordance with variousembodiments of the present disclosure;

FIG. 60 is a process flow for allowing a user to initiate communicationsessions within an IETM environment in accordance with variousembodiments of the present disclosure;

FIG. 61A is an example of a selection mechanism to enable a user toaccess communication session functionality in accordance with variousembodiments of the present disclosure;

FIG. 61B is an example of a display to enable a user to initiate acommunication session within an IETM in accordance with variousembodiments of the present disclosure;

FIG. 61C is an example of a communication window that is displayed oncea communication session is established in accordance with variousembodiments of the present disclosure;

FIG. 61D is an example of a communication window in which a user hasshared his or her window to other users involved in a communicationsession in accordance with various embodiments of the presentdisclosure;

FIG. 62 is a process flow for addressing warnings and/or cautions shownon a caution panel found on an item in accordance with variousembodiments of the present disclosure;

FIG. 63A provides an example of a virtual caution panel in accordancewith various embodiments of the present disclosure;

FIG. 63B provides an example of a corrective action provided for one ormore warnings and/or cautions in accordance with various embodiments ofthe present disclosure;

FIG. 64 is a process flow for generating a workflow for loading articlesonto and/or into an object of an item in accordance with variousembodiments of the present disclosure;

FIG. 65A provides an example of a display of a digital model of anaircraft to be loaded with articles in accordance with variousembodiments of the present disclosure;

FIG. 65B provides an example of display of a digital workflow in theform of a table of contents in accordance with various embodiments ofthe present disclosure;

FIG. 66 is a process flow for managing a workflow for loading articlesonto and/or into an object for an item in accordance with variousembodiments of the present disclosure;

FIG. 67 is a process flow for securely integrating the use of a networkconnected with a remote device with an IETM environment in accordancewith various embodiments of the present disclosure;

FIG. 68 is a process flow for providing a virtual network within an IETMenvironment in accordance with various embodiments of the presentdisclosure; and

FIG. 69 is a process flow for importing data for the technicaldocumentation for an item into an IETM in accordance with variousembodiments of the present disclosure.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments of the present disclosure now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the disclosure are shown. Indeed, thedisclosure may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” (also designated as “/”) is usedherein in both the alternative and conjunctive sense, unless otherwiseindicated. The terms “illustrative” and “exemplary” are used to beexamples with no indication of quality level. Like numbers refer to likeelements throughout.

Exemplary Technical Contributions

Various embodiments of the present disclosure address technical problemsrelated to providing technical documentation within an IETM environment.Although conventional IETMs oftentimes provide interactive functionalityto users who are viewing technical documentation via the IETMs, suchfunctionality is normally limited to simply viewing the documentation indifferent formats. For example, a conventional IETM may provide adigital model of an apparatus, machine, vehicle, equipment, and/or thelike (e.g., illustrations) that allows the user to select a componentfor the apparatus, machine, vehicle, equipment, and/or the likedisplayed in the model to view documentation on the component. However,this capability is typically the extent of the interactive functionalityprovided in the IETM. Therefore, if the user needs to perform additionaltasks with respect to the component such as, for example, ordering thecomponent, then the user is required to sign into a different system(e.g., procurement system) to perform such tasks. Such requirements notonly lead to inefficiencies with respect to resources such as the user'stime and effort jumping back and forth between different systems, butalso lead to inefficiencies with respect to resources such as thesystems, storage, networking, and/or equipment required to perform suchtasks.

In addition, requiring users to use multiple systems to view technicaldocumentation on an apparatus, machine, vehicle, equipment, and/or thelike and perform various tasks with respect to the apparatus, machine,vehicle, equipment, and/or the like can present many technicalchallenges. For instance, requiring users who are viewing technicaldocumentation through an IETM to use other systems to perform tasksoutside of viewing the documentation necessitates separate securitymeasures to be implemented within the multiple systems. Managing theseseparate security measures within each of the systems can lead tomultiple challenges in providing secure environments, as well as tofurther inefficiencies for users, systems, storage, networking, and/orequipment.

Further, users oftentimes wish to view and interact with a large volumeof technical documentation at any given time while viewing andinteracting with such documentation via an IETM. For instance, thislarge volume of documentation may involve viewing and interacting withtextual documentation and/or media content (e.g., illustrations) onseveral different topics. For example, a user may be performingmaintenance on a component and may wish to view technical documentationvia the IETM on the component, on a maintenance procedure the user isperforming on the component, as well as on a part being used inperforming the maintenance procedure. Here, the user may need to viewthe technical documentation for the different topics by interchangeablymoving back-and-forth between the technical documentation for thedifferent topics. However, a technical challenge often encountered inconventional IETMs is facilitating the user's ability to moveback-and-forth between technical documentation for different topics.Especially, when the technical documentation involves a large volume ofinformation.

Thus, various embodiments of the present disclosure address theabove-mentioned technical problems and challenges encountered with manyconventional IETMs. Specifically, various embodiments of the presentdisclosure provide functionality beyond simply presenting an interactiveenvironment to view technical documentation on items found inconventional IETMs. In addition, various embodiments of the presentdisclosure provide such functionality within a secure environment thatis more easily administered and maintained over conventionalconfigurations involving a user having to use multiple systems toperform such functionality. Furthermore, various embodiments of thepresent disclosure facilitate the display of and interaction withtechnical documentation within an IETM environment by presenting suchtechnical documentation though the use of displaying, positioning,and/or organizing of the technical documentation in a more optimalmanner over conventional IETMs through the user of unique and novelconfigurations of display windows, view panes, and/or the like.

Therefore, the disclosed solution provided herein is more effective,efficient, timely, accurate, faster, and provides more functionalitythan found in conventional IETMs. In addition, the incorporation of suchfunctionality into an IETM enables users to use such functionality in amore secure environment. Further, the disclosed solution provided hereinenables presentation of technical documentation in a more optimal mannerover conventional IETMs to facilitate the use of such documentation.Incorporating such functionality and presentation of technicaldocumentation provides the advantage of allowing user to carry out manytasks in a shorter timeframe than under conventional IETMs. Finally, thedisclosed solution can result in reduced network traffic, require fewercomputational resources, allow for less memory usage, and/or the like.Thus, various embodiments of the present disclosure make significanttechnical contributions to improving the efficiency, reliability, andfunctionality in providing technical documentation within an IETMenvironment.

Computer Program Products, Systems, Methods, and Computing Entities

Embodiments of the present disclosure may be implemented in variousways, including as computer program products that comprise articles ofmanufacture. Such computer program products may include one or moresoftware components including, for example, software objects, methods,data structures, and/or the like. A software component may be coded inany of a variety of programming languages. An illustrative programminglanguage may be a lower-level programming language such as an assemblylanguage associated with a particular hardware architecture and/oroperating system platform. A software component comprising assemblylanguage instructions may require conversion into executable machinecode by an assembler prior to execution by the hardware architectureand/or platform. Another example programming language may be ahigher-level programming language that may be portable across multiplearchitectures. A software component comprising higher-level programminglanguage instructions may require conversion to an intermediaterepresentation by an interpreter or a compiler prior to execution.

Other examples of programming languages include, but are not limited to,a macro language, a shell or command language, a job control language, ascript language, a database query or search language, and/or a reportwriting language. In one or more example embodiments, a softwarecomponent comprising instructions in one of the foregoing examples ofprogramming languages may be executed directly by an operating system orother software component without having to be first transformed intoanother form. A software component may be stored as a file or other datastorage construct. Software components of a similar type or functionallyrelated may be stored together such as, for example, in a particulardirectory, folder, or library. Software components may be static (e.g.,pre-established or fixed) or dynamic (e.g., created or modified at thetime of execution).

A computer program product may include a non-transitorycomputer-readable storage medium storing applications, programs, programmodules, scripts, source code, program code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like (also referred to herein as executable instructions,instructions for execution, computer program products, program code,and/or similar terms used herein interchangeably). Such non-transitorycomputer-readable storage media include all computer-readable media(including volatile and non-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), double datarate synchronous dynamic random access memory (DDR SDRAM), double datarate type two synchronous dynamic random access memory (DDR2 SDRAM),double data rate type three synchronous dynamic random access memory(DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), TwinTransistor RAM (TTRAM), Thyristor RAM (T-RAM), Zero-capacitor (Z-RAM),Rambus in-line memory module (RIMM), dual in-line memory module (DIMM),single in-line memory module (SIMM), video random access memory (VRAM),cache memory (including various levels), flash memory, register memory,and/or the like. It will be appreciated that where embodiments aredescribed to use a computer-readable storage medium, other types ofcomputer-readable storage media may be substituted for or used inaddition to the computer-readable storage media described above.

As should be appreciated, various embodiments of the present disclosuremay also be implemented as methods, apparatus, systems, computingdevices, computing entities, and/or the like. As such, embodiments ofthe present disclosure may take the form of a data structure, apparatus,system, computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. Thus, embodiments of the present disclosuremay also take the form of an entirely hardware embodiment, an entirelycomputer program product embodiment, and/or an embodiment that comprisesa combination of computer program products and hardware performingcertain steps or operations.

Embodiments of the present disclosure are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computing devices,computing entities, and/or the like carrying out instructions,operations, steps, and similar words used interchangeably (e.g., theexecutable instructions, instructions for execution, program code,and/or the like) on a computer-readable storage medium for execution.For example, retrieval, loading, and execution of code may be performedsequentially, such that one instruction is retrieved, loaded, andexecuted at a time. In some exemplary embodiments, retrieval, loading,and/or execution may be performed in parallel, such that multipleinstructions are retrieved, loaded, and/or executed together. Thus, suchembodiments can produce specifically configured machines performing thesteps or operations specified in the block diagrams and flowchartillustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

Exemplary System Architecture

FIG. 1 provides an illustration of an exemplary system architecture thatmay be used in accordance with various embodiments of the presentdisclosure. As shown in FIG. 1 , the architecture may include one ormore management computing entities 100, one or more networks 105, andone or more user computing entities 110. Each of these components,entities, devices, systems, and similar words used hereininterchangeably may be in direct or indirect communication with, forexample, one another over the same or different wired or wirelessnetworks. Additionally, while FIG. 1 illustrates the various systementities as separate, standalone entities, the various embodiments arenot limited to this particular architecture.

Exemplary Management Computing Entity

FIG. 2 provides a schematic of a management computing entity 100according to one embodiment of the present disclosure. In general, theterms computing entity, computer, entity, device, system, and/or similarwords used herein interchangeably may refer to, for example, one or morecomputers, computing entities, desktop computers, mobile phones,tablets, phablets, notebooks, laptops, distributed systems, gamingconsoles (e.g., Xbox, Play Station, Wii), watches, glasses, iBeacons,proximity beacons, key fobs, radio frequency identification (RFID) tags,ear pieces, scanners, televisions, dongles, cameras, wristbands,wearable items/devices, kiosks, input terminals, servers or servernetworks, blades, gateways, switches, processing devices, processingentities, set-top boxes, relays, routers, network access points, basestations, the like, and/or any combination of devices or entitiesadapted to perform the functions, operations, and/or processes describedherein. Such functions, operations, and/or processes may include, forexample, transmitting, receiving, operating on, processing, displaying,storing, determining, creating/generating, monitoring, evaluating,comparing, and/or similar terms used herein interchangeably. In oneembodiment, these functions, operations, and/or processes can beperformed on data, content, information, and/or similar terms usedherein interchangeably.

As indicated, in one embodiment, the management computing entity 100 mayalso include one or more communications interfaces 220 for communicatingwith various computing entities, such as by communicating data, content,information, and/or similar terms used herein interchangeably that canbe transmitted, received, operated on, processed, displayed, stored,and/or the like. For instance, the management computing entity 100 maycommunicate with user computing entities 110 and/or a variety of othercomputing entities.

As shown in FIG. 2 , in one embodiment, the management computing entity100 may include or be in communication with one or more processingelements 205 (also referred to as processors, processing circuitry,and/or similar terms used herein interchangeably) that communicate withother elements within the management computing entity 100 via a bus, forexample. As will be understood, the processing element 205 may beembodied in a number of different ways. For example, the processingelement 205 may be embodied as one or more complex programmable logicdevices (CPLDs), microprocessors, multi-core processors, coprocessingentities, application-specific instruction-set processors (ASIPs),microcontrollers, and/or controllers. Further, the processing element205 may be embodied as one or more other processing devices orcircuitry. The term circuitry may refer to an entirely hardwareembodiment or a combination of hardware and computer program products.Thus, the processing element 205 may be embodied as integrated circuits,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), programmable logic arrays (PLAs), hardwareaccelerators, other circuitry, and/or the like. As will therefore beunderstood, the processing element 205 may be configured for aparticular use or configured to execute instructions stored in volatileor non-volatile media or otherwise accessible to the processing element205. As such, whether configured by hardware or computer programproducts, or by a combination thereof, the processing element 205 may becapable of performing steps or operations according to embodiments ofthe present disclosure when configured accordingly.

In one embodiment, the management computing entity 100 may furtherinclude or be in communication with non-volatile media (also referred toas non-volatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In one embodiment, thenon-volatile storage or memory may include one or more non-volatilestorage or memory media 210, including but not limited to hard disks,ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, MemorySticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipedememory, racetrack memory, and/or the like. As will be recognized, thenon-volatile storage or memory media may store databases, databaseinstances, database management systems, data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like. The term database, database instance, database managementsystem, and/or similar terms used herein interchangeably may refer to acollection of records or data that is stored in a computer-readablestorage medium using one or more database models, such as a hierarchicaldatabase model, network model, relational model, entity-relationshipmodel, object model, document model, semantic model, graph model, and/orthe like.

In one embodiment, the management computing entity 100 may furtherinclude or be in communication with volatile media (also referred to asvolatile storage, memory, memory storage, memory circuitry and/orsimilar terms used herein interchangeably). In one embodiment, thevolatile storage or memory may also include one or more volatile storageor memory media 215, including but not limited to RAM, DRAM, SRAM, FPMDRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM,T-RAM, Z-RAM, RIMM, DEVIM, SIMM, VRAM, cache memory, register memory,and/or the like. As will be recognized, the volatile storage or memorymedia may be used to store at least portions of the databases, databaseinstances, database management systems, data, applications, programs,program modules, scripts, source code, object code, byte code, compiledcode, interpreted code, machine code, executable instructions, and/orthe like being executed by, for example, the processing element 205.Thus, the databases, database instances, database management systems,data, applications, programs, program modules, scripts, source code,object code, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like may be used to control certainaspects of the operation of the management computing entity 100 with theassistance of the processing element 205 and operating system.

As indicated, in one embodiment, the management computing entity 100 mayalso include one or more communications interfaces 220 for communicatingwith various computing entities, such as by communicating data, content,information, and/or similar terms used herein interchangeably that canbe transmitted, received, operated on, processed, displayed, stored,and/or the like. Such communication may be executed using a wired datatransmission protocol, such as fiber distributed data interface (FDDI),digital subscriber line (DSL), Ethernet, asynchronous transfer mode(ATM), frame relay, data over cable service interface specification(DOCSIS), or any other wired transmission protocol. Similarly, themanagement computing entity 100 may be configured to communicate viawireless external communication networks using any of a variety ofprotocols, such as general packet radio service (GPRS), Universal MobileTelecommunications System (UMTS), Code Division Multiple Access 2000(CDMA2000), CDMA2000 1× (1×RTT), Wideband Code Division Multiple Access(WCDMA), Time Division-Synchronous Code Division Multiple Access(TD-SCDMA), Long Term Evolution (LTE), Evolved Universal TerrestrialRadio Access Network (E-UTRAN), Evolution-Data Optimized (EVDO), HighSpeed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA),IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX), ultra wideband (UWB),infrared (IR) protocols, near field communication (NFC) protocols,Wibree, Bluetooth protocols, wireless universal serial bus (USB)protocols, and/or any other wireless protocol.

Although not shown, the management computing entity 100 may include orbe in communication with one or more input elements, such as a keyboardinput, a mouse input, a touch screen/display input, motion input,movement input, audio input, pointing device input, joystick input,keypad input, and/or the like. The management computing entity 100 mayalso include or be in communication with one or more output elements(not shown), such as audio output, video output, screen/display output,motion output, movement output, and/or the like.

As will be appreciated, one or more of the management computing entity's100 components may be located remotely from other management computingentity 100 components, such as in a distributed system. Furthermore, oneor more of the components may be combined and additional componentsperforming functions described herein may be included in the managementcomputing entity 100. Thus, the management computing entity 100 can beadapted to accommodate a variety of needs and circumstances. As will berecognized, these architectures and descriptions are provided forexemplary purposes only and are not limiting to the various embodiments.

Exemplary User Computing Entity

A user may be an individual, a family, a company, an organization, anentity, a department within an organization, a representative of anorganization and/or person, and/or the like. To do so, a user mayoperate a user computing entity 110 that includes one or more componentsthat are functionally similar to those of the management computingentity 100. FIG. 3 provides an illustrative schematic representative ofa user computing entity 110 that can be used in conjunction withembodiments of the present disclosure. In general, the terms device,system, computing entity, entity, and/or similar words used hereininterchangeably may refer to, for example, one or more computers,computing entities, desktops, mobile phones, tablets, phablets,notebooks, laptops, distributed systems, gaming consoles (e.g., Xbox,Play Station, Wii), watches, glasses, key fobs, radio frequencyidentification (RFID) tags, ear pieces, scanners, cameras, wristbands,kiosks, input terminals, servers or server networks, blades, gateways,switches, processing devices, processing entities, set-top boxes,relays, routers, network access points, base stations, the like, and/orany combination of devices or entities adapted to perform the functions,operations, and/or processes described herein. User computing entities110 can be operated by various parties. As shown in FIG. 3 , the usercomputing entity 110 can include an antenna 312, a transmitter 304(e.g., radio), a receiver 306 (e.g., radio), and a processing element308 (e.g., CPLDs, microprocessors, multi-core processors, coprocessingentities, ASIPs, microcontrollers, and/or controllers) that providessignals to and receives signals from the transmitter 304 and receiver306, respectively.

The signals provided to and received from the transmitter 304 and thereceiver 306, respectively, may include signaling information inaccordance with air interface standards of applicable wireless systems.In this regard, the user computing entity 110 may be capable ofoperating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, theuser computing entity 110 may operate in accordance with any of a numberof wireless communication standards and protocols, such as thosedescribed above with regard to the management computing entity 100. In aparticular embodiment, the user computing entity 110 may operate inaccordance with multiple wireless communication standards and protocols,such as UMTS, CDMA2000, 1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO,HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth, USB,and/or the like. Similarly, the user computing entity 110 may operate inaccordance with multiple wired communication standards and protocols,such as those described above with regard to the management computingentity 100 via a network interface 320.

Via these communication standards and protocols, the user computingentity 110 can communicate with various other entities using conceptssuch as Unstructured Supplementary Service Data (USSD), Short MessageService (SMS), Multimedia Messaging Service (MMS), Dual-ToneMulti-Frequency Signaling (DTMF), and/or Subscriber Identity ModuleDialer (SIM dialer). The user computing entity 110 can also downloadchanges, add-ons, and updates, for instance, to its firmware, software(e.g., including executable instructions, applications, programmodules), and operating system.

According to one embodiment, the user computing entity 110 may includelocation determining aspects, devices, modules, functionalities, and/orsimilar words used herein interchangeably. For example, the usercomputing entity 110 may include outdoor positioning aspects, such as alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, universal time(UTC), date, and/or various other information/data. In one embodiment,the location module can acquire data, sometimes known as ephemeris data,by identifying the number of satellites in view and the relativepositions of those satellites. The satellites may be a variety ofdifferent satellites, including Low Earth Orbit (LEO) satellite systems,Department of Defense (DOD) satellite systems, the European UnionGalileo positioning systems, the Chinese Compass navigation systems,Indian Regional Navigational satellite systems, and/or the like.Alternatively, the location information can be determined bytriangulating the user computing entity's 110 position in connectionwith a variety of other systems, including cellular towers, Wi-Fi accesspoints, and/or the like. Similarly, the user computing entity 110 mayinclude indoor positioning aspects, such as a location module adapted toacquire, for example, latitude, longitude, altitude, geocode, course,direction, heading, speed, time, date, and/or various otherinformation/data. Some of the indoor systems may use various position orlocation technologies including RFID tags, indoor beacons ortransmitters, Wi-Fi access points, cellular towers, nearby computingdevices (e.g., smartphones, laptops) and/or the like. For instance, suchtechnologies may include the iBeacons, Gimbal proximity beacons,Bluetooth Low Energy (BLE) transmitters, NFC transmitters, and/or thelike. These indoor positioning aspects can be used in a variety ofsettings to determine the location of someone or something to withininches or centimeters.

The user computing entity 110 may also comprise an IETM viewer (that caninclude a display 316 coupled to a processing element 308) and/or aviewer (coupled to a processing element 308). For example, the IETMviewer may be a user application, browser, user interface, graphicaluser interface, and/or similar words used herein interchangeablyexecuting on and/or accessible via the user computing entity 110 tointeract with and/or cause display of information from the managementcomputing entity 100, as described herein. The term “viewer” is usedgenerically and is not limited to “viewing.” Rather, the viewer is amulti-purpose digital data viewer capable and/or receiving input andproviding output. The viewer can comprise any of a number of devices orinterfaces allowing the user computing entity 110 to receive data, suchas a keypad 318 (hard or soft), a touch display, voice/speech or motioninterfaces, or other input device. In embodiments including a keypad318, the keypad 318 can include (or cause display of) the conventionalnumeric (0-9) and related keys (#, *), and other keys used for operatingthe user computing entity 110 and may include a full set of alphabetickeys or set of keys that may be activated to provide a full set ofalphanumeric keys. In addition to providing input, the viewer can beused, for example, to activate or deactivate certain functions, such asscreen savers and/or sleep modes.

The user computing entity 110 can also include volatile storage ormemory 322 and/or non-volatile storage or memory 324, which can beembedded and/or may be removable. For example, the non-volatile memorymay be ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards,Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM,Millipede memory, racetrack memory, and/or the like. The volatile memorymay be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM,cache memory, register memory, and/or the like. The volatile andnon-volatile storage or memory can store databases, database instances,database management systems, data, applications, programs, programmodules, scripts, source code, object code, byte code, compiled code,interpreted code, machine code, executable instructions, and/or the liketo implement the functions of the user computing entity 110. Asindicated, this may include a user application that is resident on theentity or accessible through a browser or other IETM viewer forcommunicating with the management computing entity 100 and/or variousother computing entities.

In another embodiment, the user computing entity 110 may include one ormore components or functionality that are the same or similar to thoseof the management computing entity 100, as described in greater detailabove. As will be recognized, these architectures and descriptions areprovided for exemplary purposes only and are not limiting to the variousembodiments.

Exemplary System Operations

The logical operations described herein may be implemented (1) as asequence of computer implemented acts or one or more program modulesrunning on a computing system and/or (2) as interconnected machine logiccircuits or circuit modules within the computing system. Theimplementation is a matter of choice dependent on the performance andother requirements of the computing system. Accordingly, the logicaloperations described herein are referred to variously as states,operations, structural devices, acts, or modules. These states,operations, structural devices, acts, and modules may be implemented insoftware, in firmware, in special purpose digital logic, and anycombination thereof. Greater or fewer operations may be performed thanshown in the figures and described herein. These operations may also beperformed in a different order than those described herein.

As described above, the management computing entity 100 and/or usercomputing entity 110 may be configured for storing technicaldocumentation (e.g., data) in an IETM, providing access to the technicaldocumentation to a user via the IETM, and/or providing functionality tothe user accessing the technical documentation via the IETM. In general,the technical documentation is typically made up of volumes of textalong with other media objects. In many instances, the technicaldocumentation is arranged to provide the text and/or the media objectson an item. For instance, the item may be a product, machinery,equipment, a system, and/or the like such as, for example, a bicycle oran aircraft.

Accordingly, the technical documentation may provide textual informationalong with non-textual information (e.g., one or more visualrepresentations) of the item and/or components of the item. Textualinformation generally includes alphanumeric information and may alsoinclude different element types such as graphical features, controls,and/or the like. Non-textual information generally includes mediacontent such as illustrations (e.g., 2D and 3D graphics), video, audio,and/or the like. Although the non-textual information may also includealphanumeric information.

The technical documentation may be provided as digital media in any of avariety of formats, such as JPEG, JFIF, JPEG2000, EXIF, TIFF, RAW, DIV,GIF, BMP, PNG, PPM, MOV, AVI, MP4, MKV, and/or the like. In addition,the technical documentation may be provided in any of a variety offormats, such as DOCX, HTMLS, TXT, PDF, XML, SGML, JSON and/or the like.As noted, the technical documentation may provide textual andnon-textual information of various components of the item. For example,various information may be provided with respect to assemblies,sub-assemblies, sub-sub-assemblies, systems, subsystems, sub-subsystems,individual parts, and/or the like associated with the item.

In various embodiments, the technical documentation for the item may bestored and/or provided in accordance with S1000D standards and/or avariety of other standards. According to various embodiments, themanagement computing entity 100 and/or user computing entity 110provides functionality in the access and use of the technicaldocumentation provided via the IETM in accordance with user instructionsand/or input received from the user via an IETM viewer (e.g., a browser,a window, an application, a graphical user interface, and/or the like).

Accordingly, in particular embodiments, the IETM viewer is accessiblefrom a user computing entity 110 that may or may not be in communicationwith the management computing entity 100. For example, a user may signinto the management computing entity 100 from the user computing entity110 or solely into the user computing entity 110 to access technicaldocumentation via the IETM and the management computing entity 100and/or user computing entity 110 may be configured to recognize any suchsign in request, verify the user has permission to access the technicaldocumentation (e.g., by verifying the user's credentials), andpresent/provide the user with various displays of content for thetechnical documentation via the IETM viewer (e.g., displayed on display316).

Further detail is now provided with respect to various functionalityprovided by embodiments of the present disclosure. As one of ordinaryskill in the art will understand in light of this disclosure. Themodules now discussed and configured for carrying out variousfunctionality may be invoked, executed, and/or the like by themanagement computing entity 100, the user computing entity 110, and/or acombination thereof depending on the embodiment.

Sign-in Module

A user may be required to sign-in on a device (e.g., a user computingentity 110) to gain access to the technical documentation for an itemthrough an IETM. Accordingly, depending on the circumstances, the user'sdevice (e.g., user computing entity 110) and/or a management computingentity 100 may be configured for facilitating the user's access to thetechnical documentation. For example, the technical documentation may bestored locally on the user's computing entity 110 and therefore, theuser's computing entity 110 is configured to facilitate the user'saccess to the documentation without cooperation of the managementcomputing entity 100. In other instances, the user's computing entity110 and the management computing entity 100 may be communication andwork in concert to provide access to the technical documentation to theuser.

Turning now to FIG. 4 , additional details are provided regarding aprocess flow for signing a user into the IETM according to variousembodiments. FIG. 4 is a flow diagram showing a sign-in module forperforming such functionality according to various embodiments of thedisclosure. Here, the user may open the IETM residing on his or her usercomputing entity 110 to gain access to technical documentation for aparticular item. While in other instances, the user may open an IETMviewer (e.g., browser) to gain access to the technical documentationresiding remotely on the management computing entity 100. For example,the IETM may be provided as a software-as-a-service over some type ofnetwork. Similarly, depending on the embodiment, the technicaldocumentation may be stored locally on the user's computing entity 110or remotely on the management computing entity 100 that the usercomputing entity 110 communicates with to access the documentation.

Therefore, the process flow 400 begins in various embodiments with thesign-in module providing a sign-in page (e.g., webpage), screen, window,graphical user interface, and/or the like viewable by the user via anIETM viewer in Operation 410. For convenience, the term “window” is usedthroughout the remainder of the application, although those of ordinaryskill in the art understand this term may include other forms ofdisplaying content. The sign-in window may provide a number of fieldssuch as a selectable dataset field, a selectable unit field, and aselectable object field. In particular embodiments, the selectabledataset field provides one or more datasets in which each datasetrepresents a publication of the technical documentation available for aparticular item. For example, technical documentation accessible throughthe IETM may be for an airline. Here, the airline may have a number ofdifferent aircraft types/models in its fleet such as different jetmodels, propeller models, rotor models, and/or the like. Therefore, theIETM may provide a dataset for each model and the selectable datasetfield may be a mechanism such as a dropdown field listing all of thedatasets for the different aircraft models that allows for the user toselect a particular dataset.

The sign-in module determines whether input has been received indicatingthe user has selected a dataset for a particular item in Operation 415.If so, then the sign-in module provides one or more applicable units forthe dataset for display in Operation 420. An applicable unit mayrepresent the user's relationship with respect to the technicaldocumentation and the associated item. For instance, in particularembodiments, the user may be an employee of an airline and the unit mayrepresent the position, job, role, and/or the like that the user holdswith the airline. For example, the user may be a salesperson, designengineer, mechanical, and/or the like for the airline. In otherembodiments, the unit may represent a larger entity within theorganization such as, for example, research and development department,marketing department, engineering design department, and/or the like. Inaddition, in particular embodiments, the applicable units displayed maybe dependent on the dataset selected by the user. For example, anapplicable unit that may be provided is jet mechanic as a result of theuser selecting the model of a jet dataset. Accordingly, the units may bedisplayed in the selectable unit field. For example, the selectable unitfield may be a dropdown field listing all of the applicable units forthe user to select from.

Therefore, the sign-in module determines whether input has been receivedindicating the user has selected a unit in Operation 425. If so, thenthe sign-in module in particular embodiments provides one or moreapplicable objects in the selectable object field in Operation 430.Here, an object represents a specific instance of the item associatedwith the technical documentation. For example, the user may be amechanic for the airline and he or she may be signing into the IETM togain access to technical documentation for a particular model ofaircraft. Here, the particular model of aircraft may have multipleconfigurations in which a first configuration uses air brakes and thrustreversers and a second configuration uses disc brakes and thrustreversers. Therefore, the objects may represent the two differentconfigurations of the model of aircraft. In another example, the usermay instead be a mechanic for the airline and he or she may be signinginto the IETM to gain access to technical documentation for a particularaircraft. Therefore, in this instance, the one or more applicableobjects may be the specific aircraft found in the airline's fleet forthe model of aircraft. For example, the user may be planning to performmaintenance on one of the particular aircraft and selects the aircraftfrom the applicable objects listed in the selectable object field.

Again, the selectable object field may be configured as a control suchas a dropdown listing the applicable objects to allow the user to selecta desired object. In addition, the applicable objects may be dependenton the unit selected by the user. For example, the user may haveselected mechanic for crew C as the unit and only the aircraft for theparticular type of aircraft authorized to be worked on by crew C may bedisplayed on the sign-in window.

Accordingly, in particular embodiments, selection of a particular objectmay allow for the technical documentation for the item to be filtereddown to a smaller dataset. For instance, returning to the exampleinvolving the different configurations for the model of aircraft, thetechnical documentation for this particular model of aircraft may befiltered to only provide documentation on the air brake configuration orthe disc brake configuration based at least in part on the user'sselection. In addition, in particular embodiments, a selection of aparticular object may allow for recordation of technical documentationaccessed and/or processes, tasks, and/or the like performed for aparticular object of an item. For instance, the performance ofmaintenance on a specific aircraft found in the airline's fleet may berecorded/tracked in the IETM. Therefore, the IETM may be used tomaintain a maintenance record for the specific aircraft. In someembodiments, a universal object may be provided along with theapplicable objects that allows for the user to view all the technicaldocumentation for a particular item. For example, a universal object maybe provided to allow the user to view the technical documentation onboth the air brake configuration and the disc brake configuration of themodel of aircraft.

Therefore, in particular embodiments, the sign-in module determineswhether input has been received indicating the user has selected aspecific object in Operation 435. If not, then the sign-in moduledetermines whether input has been received indicating the user hasselected a universal object in Operation 440. If the user has selectedthe universal object, then the sign-in module causes a sign-in mechanismto be made available on the sign-in window to the user in Operation 445.Accordingly, the sign-in mechanism may be any one of different types ofcontrols depending on the embodiment such as, for example, a button, atoggle, checkbox, and/or the like.

If instead the user has selected a specific object, then the sign-inmodule in particular embodiments determines whether input has beenreceived indicating a job has been identified in Operation 450. A jobmay represent an instance of a specific procedure, task, operation,and/or the like to be performed on the specific object. For instance,returning to the example involving the user selecting a specificaircraft for airline, the job may represent a specific maintenance taskthe user is to perform on the specific aircraft such as repairing theair braking system. Accordingly, the sign-in window may provide a fieldfor the user to enter an identifier for the job. In some embodiments,the sign-in module causes the job field to be accessible in response tothe user selecting a specific object.

Again, the identification of a job may allow the technical documentationto be filtered to enable the user to find the documentation needed forthe job more easily. In addition, the identification of a job may allowfor the tracking on the jobs performed on the specific object. Further,the identification of a job may provide security in that access to onlycertain technical documentation may be provided based at least in parton the job. If a job has been identified by the user, then the sign-inmodule causes the sign-in mechanism to be made available in Operation445.

At this point, the user may select the sign-in mechanism to gain accessto the IETM and desired technical documentation. Therefore, the sign-inmodule determines whether input has been received indicating the userhas selected the sign-in mechanism in Operation 455 and if so, hasprovided the required information in Operation 460. For example, inparticular embodiments, the sign-in window may also display one or morefields for the user to enter a username and/or password. Therefore, inthese instances, the sign-in module may determine whether the user hasprovided such information. If the user has not, then the sign-in modulemay provide an error message to display informing the user to providethe needed information in Operation 465.

If all the required information has been provided by the user, then thesign-in module determines whether the user's credentials are valid inOperation 470. Here, in particular embodiments, the IETM and/or asupporting system in communication with the IETM may store informationon the user's credentials and the information entered by the user on thesign-in window may be compared with the stored credential information.If the user's credentials are invalid, then the sign-in module mayprovide an error message to display informing the user of such inOperation 465. However, if the user's credentials are valid, then thesign-in module signs the user into the IETM in Operation 475. At thispoint, the user may begin accessing and interacting with the technicaldocumentation for the item via the IETM.

Turning now to FIG. 5A, an example of a sign-in window 500 is providedthat may be used according to various embodiments. In this particularexample, a username field 510 is provided as a text field that allowsfor the user to enter his or her username. In addition, a selectabledataset field 515 is provided to allow the user to select the technicaldocumentation (e.g., dataset) for a desired item. Here, the selectabledataset field 515 is provided as a dropdown menu control that lists theavailable technical documentation from which the user can select.Likewise, a selectable unit field 520 is provided that allows for theuser to select a unit. Again, in this particular example, the selectableunit field 520 is provided as a dropdown menu control listing theapplicable units for the dataset. Further, a selectable object field 525is provided that allows for the user to select a specific object for theitem. In this particular example, the objects are specific aircraftidentified by their tail numbers. Therefore, the user selects the tailnumber of the desired aircraft. In addition, a universal object 530 isprovided in the list of objects in this particular example that allowsfor the user to gain access to all of the technical documentation forthe model of aircraft (item). Here, the universal object 530 is providedso that it may be used when the user is engaging in research and/ortraining on the model of aircraft and not necessarily performing aprocedure, task, operation, and/or the like on a specific aircraft.

Turning to FIG. 5B, a job field 535 is provided to allow the user toenter a job (e.g., job identifier) with respect to the specific object.In addition, a sign-in mechanism (e.g., a button) 540 is provided thatthe user may select to sign into the IETM and view the technicaldocumentation for the specific object. As further discussed herein, theuser may now be provided with access to the technical documentation anda number of different functionality with respect to the technicaldocumentation in various embodiments.

Accordingly, the sign-in functionality provided in various embodimentsmay allow for tracking and reporting of activities within the IETM. Forinstance, any activity engaged in by the user once he or she is signedinto the IETM may be recorded and viewable via the IETM. For example,the content (e.g., the technical documentation) accessed and viewed bythe user may be recorded so that the user's access and use of suchcontent can be monitored. In addition, the user's completion ofactivities such as procedures, tasks, operations, and the like may berecorded and monitored.

For example, FIGS. 5C and 5D provide a history report 545 the user mayview via the IETM on the user's history of accessing and viewingdifferent content (e.g., data modules) in the technical documentation.The history report 545 may be configured in some embodiments to allowthe user to select particular content (e.g., a particular data module)from the report 545 to view the content in a separate view pane 550.Depending on the embodiment, the history report 545 may only be providedto the user or may be provided to other personal such as the user'ssupervisor so that the supervisor can monitor the user's activities.Other types of reports may be made available to the user such as a dailyreport 555 shown in FIG. 5D. Again, depending on the embodiment, thedaily report 555 may only be provided to the user or may be provided toother personal such as the user's supervisor. Thus, the availability ofcertain functionality within the IETM may be provided to the user andothers based at least in part on their credentials used to sign-into theIETM.

Table of Contents Module

In various embodiments, the user may be provided with an initial windowupon signing into the IETM to view the technical documentation for anitem. Accordingly, in particular embodiments, a table of contents may bedisplayed on the initial window for the technical documentationassociated with the item and various functionality. In some embodiments,the initial window may include multiple view panes. For instance, insome embodiments, the window may include a first view pane and a secondview pane that are displayed on non-overlapping portions of the window,although more than two view panes may be displayed and/or the panes maybe displayed on overlapping portions of the window in some instances.

In some embodiments, the table of contents may be displayed on a firstview pane and may provide a list of topics configured to be selectableto view information on a selected topic. For example, each of the topicsmay be provided as a hyperlink and/or provided with one or moreselection mechanisms such as buttons that a user may select to viewadditional information on the topic. Depending of the embodiment, theadditional information may then be provided for displaying on anotherview pane on the window (e.g., on the second view pane) and/or via aseparate window. In some embodiments, the separate window displaying theadditional information may be superimposed over a portion of the firstwindow displaying the table of contents.

As described further herein, other windows provided for display invarious embodiments may be configured in the same or similar fashion.Depending on the configuration, these windows may include any number ofpanes. For instances, the panes may be provided side-by-side onnon-overlapping potions of the window or may be provided as overlapping(e.g., superimposed over one another) on the window. In addition, thepanes may be displayed in various sizes and dimensions with respect tothe window. Further, the panes may be display statically and/ordynamically such as pop-up panes.

In addition, any number of separate windows may be displayed atvirtually the same time side-by-side or with one window superimposedover a portion of or an entire second window. Here, the window(s) may bedisplayed in various sizes and dimensions. In addition, in someembodiments, multiple windows may be displayed as superimposed over oneanother (or portion thereof) in a cascading fashion. Further, suchwindows may be displayed statically or dynamically such as pop-upwindows. Furthermore, a window may be provided in particular embodimentsfor display in any number of different formats such as, for example, adialog box, tooltip, infotip, tear-off window, and/or the like.

Thus, turning now to FIG. 6 , additional details are provided regardinga process flow for facilitating the user's viewing and interacting withthe table of contents according to various embodiments. FIG. 6 is a flowdiagram showing a table of contents (TOC) module for performing suchfunctionality according to various embodiments of the disclosure.

The process flow 600 begins in various embodiments with the TOC moduleproviding a window for display comprising the table of contents inOperation 610. As previously discussed, the table of contents mayprovide a list of topics on content found within the technicaldocumentation for the item. Accordingly, each of the topics may beselectable (e.g., may be configured as a hyperlink or configured withsome type of selection mechanism such as a button) to access contentfound in the technical documentation for the item.

For example, topics may include procedures, tasks, operations, services,checklists, planning, and/or the like performed with respect to theitem. For instance, topics may include maintenance procedures and/ortasks performed on the item. Therefore, the maintenance procedure (e.g.,an identifier of the maintenance procedure such as a title of themaintenance procedure) may be selected by the user directly from thetable of contents to access content found in the technical documentationfor the maintenance procedure.

In addition, topics may include different components that make up theitem. For example, a component of an aircraft is the front landingwheel. Accordingly, components may identify functional and/or physicalstructures of the item and may be broken down into assembly,sub-assembly, sub-sub-assembly, system, sub-system, sub-sub-system,subject, unit, part, and/or the like.

Further, the table of contents may be displayed in a hierarchicalstructure in which topics are grouped accordingly with some topicsnested within other topics within the hierarchical structure based atleast in part on relationships between the different topics. Forexample, a topic on the front landing wheel of an aircraft may be nestedunder a topic on the front landing gear assembly for the aircraft in thehierarchical structure of the table of contents. Lastly, the table ofcontents may provide various lists on other types of information inparticular embodiments such as lists of effective data modules,illustrations, tables, parts, orders for parts, annotations, directions,publications, and/or the like.

The user may select a topic to preview in particular embodiments. Forexample, the user may use a mouse to click on, right click on, or hoverover a topic in the table of contents or use a stylus or finger toselect a topic in the table of contents to generate a preview for thetopic. Therefore, the TOC module may determine whether input has beenreceived indicating the user has selected a topic to preview inOperation 615. If so, then the TOC module generates the topic preview inOperation 620 and provides the topic preview for display for the user toview in Operation 625.

For instance, in particular embodiments, the topic preview may beprovided as a separate window for display. Accordingly, the topicpreview may provide the user with information/data, tables,instructions, illustrations, other media content, links to additionaland/or related information, and/or the like associated with the selectedtopic. In some embodiments, the topic preview is configured to provideonly a preview of some of the content found in the technicaldocumentation on the topic. For example, the topic preview may beconfigured in particular embodiments to provide the first five to fiftylines of textual information that the user would be provided with if theuser were to select the topic to view the entire content for the topic.In addition, the preview may be superimposed over a portion of thewindow displaying the table of contents.

In some embodiments, the user may be provided with functionality tofilter the table of contents. For instance, the content for each of thetopics may be associated with metadata. Indeed, the content may beorganized based at least in part on S1000D standards. S1000D standardsrequires the content to be configured into data modules representingsmall, reusable pieces of technical information/data. Accordingly, eachdata module includes a header section configured to provideidentification information and status information for the data modulethat includes metadata for managing the data module (e.g., sourceinformation, security classification, applicability, change history,reason for change, verification status, and/or the like). Here, theheader section may include an information code that provides adescription on the type of information found in the content of the datamodule.

Therefore, in particular embodiments, functionality is provided to allowthe user to filter the table of contents using the information codes forthe different topics (e.g., data modules for the topics). Thus, in theseparticular embodiments, the TOC module determines whether input has beenreceived indicating the user would like to filter the table of contentbased at least in part on an information code (InfoCode) in Operation630. If so, then the TOC module filters the table of contents andprovides of the table for display in Operation 635.

In addition, in particular embodiments, functionality is provided toallow the user to view the table of contents in a source format asopposed to a format adhering to S1000D standards. In many instances, thesource format may be preferable for a user because the source format mayinclude labeling of the content that is better suited for searching thanthe formatting, of the content under S1000D standards. For example,S1000D standards requires the figures (e.g.; illustrations) found in adata module to be numbered always beginning with one. Therefore, ifcontent from a source is partitioned into multiple data modules, theoriginal labeling of figures may be lost. As a result, the content mayend up being displayed having multiple figures labeled the same (e.g.,may end of having multiple figures labeled as one). The same canhappened with respect to other labels found in the source content suchas chapters, headings, sub-headings, sections, sub-sections, and/or thelike. Therefore, the TOC module determines whether input has beenreceived indicating the user would like to view the table of contentsshowing the source content formatting in Operation 640. If so, then theTOC module generates and provides the table of contents with the sourcecontent formatting for display in Operation 645.

Further, in particular embodiments, functionality (e.g., a searchmechanism displayed on the window) is provided that allows the user tosearch the table of contents. As discussed further herein, the searchfunctionality may allow the user to provide criteria (e.g., one or moresearch terms) that can then be used to identify topics based at least inpart on the criteria. In some embodiments, a search window is providedon which the user can enter search terms and to display the searchresults. Therefore, in these embodiments, the TOC module determineswhether input has been received indicating the search functionality hasbeen selected by the user in Operation 650. If so, then the TOC moduleenables such functionality in Operation 655.

Furthermore, in particular embodiments, functionality is provided toallow for the user to copy the data module code (DMC) for a topic. Thedata module code is part of the metadata (e.g., header section) of adata module that holds the content for a topic. The DMC includes severalcharacters identifying information about the data module such as theitem to which the content applies, the functional or physical breakdownof the item associated with the content, the specific type ofinformation found in the content, and/or the like. Therefore, in theseparticular embodiments, the TOC module determines whether input has beenreceived indicating the user would like to copy the DMC for a particulartopic (e.g., particular data module) in Operation 660. For example, theuser may select a topic in the table of contents using shift click tocopy the DMC for the topic. If so, then the TOC module copies the DMC inOperation 665. For instance, the TOC module may copy the DMC from a URI,displayed via the IETM viewer (e.g., for the corresponding data module).In some embodiments, the user may then send the URL in some type ofcommunication (e.g., in an email) to another individual. For example,the user may wish to send a message to an individual who is managing thecontent of the data module asking the individual to make a change to thedata module. Therefore, the user may wish to include the DMC for thedate module to identify which data module the user is talking about.

Finally, the TOC module is configured in various embodiments todetermine whether input has been received indicating the user hasselected a particular topic to view in Operation 670. For instance, inparticular embodiments, the TOC module may be configured to determinethe user using a first type of selection mechanism (e.g., hover over atopic in the table of contents) to generate and provide a topic previewof the content for the topic and determine the user using a second,different type of selection mechanism (e.g., a mouse click on the topicin the table of contents) to generate and provide the content found inthe technical documentation for the topic. Again, the selectionmechanism may involve the user using some type of control such as amouse to click on, right click on, or hover over the topic in the tableof contents or use a stylus or finger to select a topic in the table ofcontents, Therefore, if the TOC module determines the user has selecteda topic to view in the IETM, then the TOC module provides the topic todisplay in Operation 675.

Accordingly, depending on the embodiment, the content for the topic maybe displayed on the same or a different window. For instance, inparticular embodiments, the content for the topic may be displayed in aseparate view pane (e.g., second view pane) on the window. In otherembodiments, the content may be displayed on a different window whilethe window displaying the table of contents may still be available forviewing. For example, the window displaying the table of contents may beavailable for immediate viewing in response to the user selecting amechanism such as a button displayed on a toolbar and/or a view tab viathe IETM viewer.

Turning briefly to FIG. 7 , an example of a table of contents displayedaccording to various embodiments is shown. Here, the table of contentsincludes a preface 700 of different lists along with a list of varioustopics. In this example, the user has selected a particular topic 715 togenerate a preview for the topic that is being displayed on a separatewindow 720. In addition, the window provides a selectable field 725(e.g., a dropdown menu control) to allow the user to filter the table ofcontents based at least in part on information codes. Further, thepreview window 720 in this example provides a selection mechanism (e.g.,a button) 730 to add a bookmark for the preview. Bookmarking the previewmay allow the user to recall the preview and/or content for theassociated topic at a later time to view. Accordingly, such a bookmarkmay be recorded and saved in the IETM for the user.

Further detail is now provided with respect to functionality availablein various embodiments for the table of contents. Specifically,different modules are discussed that may be invoked in variousembodiments by the TOC module to facilitate such functionality.

Filtering Module

Turning now to FIG. 8 , additional details are provided regarding aprocess flow for filtering the table of contents based at least in parton an information code according to various embodiments. FIG. 8 is aflow diagram showing a filtering module for performing suchfunctionality according to various embodiments of the disclosure. Inparticular embodiments, the filtering module may be invoked by anothermodule to filter the table of contents such as, for example, the TOCmodule previously described. However, with that said, the filteringmodule may not necessarily be invoked by another module and may executeas a stand-alone module in other embodiments.

Accordingly, the filtering module may be invoked in some embodiments asa result of the user identifying a particular information code to use infiltering the table of contents. Here, the technical documentation mayinclude publication data (e.g., a publication module). In theseparticular embodiments, the publication data may provide a list oftechnical data (e.g., every data module) found in the publication of thetechnical documentation for the item in the order in which thepublication delivers the data to the IETM. Therefore, the publicationdata may provide a navigation structure for the IETM in constructing thetable of contents.

Therefore, the process flow 800 may begin with the filtering modulereferencing the publication data in Operation 810. The filtering modulethen select specific data (e.g., a data module) found in the publicationdata in Operation 815. In addition to identifying the technical datafound in the publication of the technical documentation, the publicationdata may also include metadata (e.g., the DMC) for the technical data(e.g., for each of the data modules). Therefore, the filtering modulereads the information code for the selected data in Operation 820. Thefiltering module then determines whether the information code for theselected data matches the information code selected by the user tofilter the table of contents in Operation 825. If so, then the filteringmodule marks the technical data for displaying as a topic in thefiltered table of contents in Operation 830.

At this point, the filtering module determines whether the publicationmodule contains additional technical data (e.g., another data module) inthe list of technical data in Operation 835. If so, then the filteringmodule returns to Operation 815, selects the next technical data foundin the list (e.g., the next data module), and repeats the operationsjust described for the newly selected technical data. Once all of thetechnical data have been processed in the list, the filtering modulethen generates and provides the results for display to the user inOperations 840 and 845.

Turning now to FIG. 9 , an example of the results of filtering the tableof contents based at least in part on an information code is provided.In this example, the table of contents has been filtered based at leastin part on the information code for troubleshooting 900. As the readercan see, only those topics 910 dealing with troubleshooting are shownunder the topic heading fuel and topic sub-headings distribution andgeneral. Thus, the filter function provided in various embodimentsallows for the user to filter down the topics found in the technicaldocumentation in a faster, more efficient manner so that the user canmore easily and quickly identify needed content in the technicaldocumentation.

Source Format Tagging Module

As previously described, functionality may be provided in someembodiments to allow the user to view the table of contents in a sourceformat as opposed to a format adhering to S1000D standards. As noted,the source format may be preferable for a user because the source formatmay include labeling of the content that is better suited for searchingthan the formatting of the content under S1000D standards.

Turning now to FIG. 10 , additional details are provided regarding aprocess flow for tagging content with the formatting found in the sourceof the content according to various embodiments. FIG. 10 is a flowdiagram showing a source format tagging module for performing suchfunctionality according to various embodiments of the disclosure.Accordingly, the source format tagging module may be executed inparticular embodiments by an entity such as the management computingentity 100 and/or a user computing entity 110 engaged in importing apublication of technical documentation for an item into the IETM. Inthis instance, the publication may include content from a source in aformat such as portable document format (PDF), a standards generalizedmarkup language (SGML) format, and/or the like. The source may includeformatting for the content such as identifiers (e.g., numbering and/ortextual descriptions) for chapters, headings, sub-headings, sections,tables, figures, and/or the like.

Therefore, the process flow 1000 begins with the source format taggingmodule reading the information from such a source in Operation 1010. Thesource format tagging module then selects the format structure from theinformation in Operation 1015 and tags the appropriate portion of thecontent with the information in Operation 1020. For instance, inparticular embodiments, the source format tagging module may recordmetadata along with the content from the source in the IETM thatincludes the source formatting and information to format the contentappropriately. For example, the content may include a reference to afigure and the source format tagging module may record the format (e.g.,the label) for the figure in metadata along with the content in theIETM. While in another example, the content found in the source mayinclude a chapter title. Therefore, the source format tagging module mayrecord the title of the chapter in the metadata along with the contentin the IETM.

At this point, the format tagging module determines whether additionalformat structure is found in the content in Operation 1025. If so, thenthe source format tagging module returns to Operation 1015, selects thenext format structure found in the content, and tags the content withthe format structure accordingly. As a result, the content can bedisplayed in various embodiments in its original format structure fromthe source of the content.

Source Formatting Module

Turning now to FIG. 11 , additional details are provided regarding aprocess flow for formatting content based at least in part on a formatstructure found in the source of the content according to variousembodiments. FIG. 11 is a flow diagram showing a source formattingmodule for performing such functionality according to variousembodiments of the disclosure. In this instance, the user may wish toview the table of contents with the topics shown with the formatstructure found in the source of the topics. Therefore, in particularembodiments, the source formatting module may be invoked by anothermodule to display the content with the format structure from the sourcesuch as, for example, the TOC module previously described. However, withthat said, the source formatting module may not necessarily be invokedby another module and may execute as a stand-alone module in otherembodiments.

The process flow 1100 begins with the source formatting module reading aformat tag for the content in Operation 1110. As previously discussed,the content may be tagged in particular embodiments by includingmetadata (e.g., tags) long with the content identifying various parts ofthe format structure found in the source of the content. For example,the metadata may include one or more tags providing identifiers (e.g.,numbering and/or textual descriptions) for chapters, headings,sub-headings, sections, tables, figures, and/or the like found in thesource of the content.

The source formatting module then formats the content based at least inpart on the format structure found in the tag in Operation 1115. Forexample, the format structure may identify a subject matter heading forthe content. Therefore, the source formatting module may format thecontent with the subject matter heading. Accordingly, in particularinstances, the content may then be found in the table of contents as atopic having the subject matter heading as a title. While in otherinstances, the content itself may be displayed on a window with thesubject matter heading.

At this point, the source formatting module determines whether anothertag exists for the content in Operation 1120. If so, then the sourceformatting module returns to Operation 1110, reads the next tag for thecontent, and formats the content based at least in part on the formatstructure found in the tag.

Turning to FIG. 12A, an example is provided of a table of contents 1200formatted according to S1000D standards. As shown in the figure, all ofthe topics found under the heading flight manual are provided in ageneric format with only a title for each topic. However, in FIG. 12B,the table of contents 1210 is now formatted using the format structurefound in the source for the flight manual. As the reader can see, eachof the topics is now listed with a section heading as found in thesource for the flight manual. Such section headings may allow for theuser to more easily distinguish between the different content providedby the source.

Another example is shown in FIG. 12C. In this example, content from asource, in this instance a PDF file, is being displayed on a window withsource formatting according to various embodiments. Here, the formatstructure of the content shown on the window matches the formatstructure of the content found in the source PDF file. Specifically, thetitle designator for the content 1215 has been included along with thetitle of the content 1220 shown on the window. In addition, the heading1225 and sub-headings 1235, 1245 from the source PDF file are shown as aheading 1230 and sub-headings 1240, 1250 in the content on the window.Here, in the example, the user may be able to better navigate andunderstand the content as a result of viewing the content in the formatstructure found in the source PDF file.

Search Module

As previously noted, the user may conduct a search of the elements(e.g., topics and/or lists) found in the table of contents based atleast in part on criteria (e.g., one or more search terms). Turning nowto FIG. 13 , additional details are provided regarding a process flowfor searching the table of contents according to various embodiments.FIG. 13 is a flow diagram showing a search module for performing suchfunctionality according to various embodiments of the disclosure. Inparticular embodiment, the search module may be invoked by anothermodule to search the table of contents such as, for example, the TOCmodule previously described. For instance, a user may select a mechanism(e.g., button) provided on a window displaying the table of contents andas a result, the TOC module may invoke the search module. However, withthat said, the search module may not necessarily be invoked by anothermodule and may execute as a stand-alone module in other embodiments.

The process flow 1300 begins with the search module providing a searchwindow for display to the user in Operation 1310. Accordingly, thesearch window may be configured in a similar fashion as the windowdisplaying the table of contents. For instance, in some embodiments, thesearch window may include one or more view panes for displaying searchresults according to different criteria (e.g., different features of theelements found in the table of contents). In particular embodiments. thesearch window provides a freeform field that allows the user to type inone or more search terms to use in searching the table of contents. 111some embodiments, the search module may be configured to providepredictions of search terms to the user based at least in part on thecharacters typed into the freeform field.

Therefore, in these embodiments, the search module determines whetherinput has been received indicating the user has typed one or morecharacters into the freeform field in Operation 1315. If so, then thesearch module provides one or more predictions of search terms (e.g.,autocomplete) to the user in Operation 1320. As discussed furtherherein, the predictions may be based at least in part on differentgrounds depending on the embodiment. For example, the search module maybe configured to provide the first five predictions identified for theentered characters alphabetically, based at least in part on frequencyof use, based at least in part on recent trends, and/or the like.

The search module then determines whether input has been receivedindicating the user has initiated a search based at least in part on theentered search terms) in Operation 1325. For instance, the search windowmay include a selection mechanism (e.g., a button) that the user canselect to initiate the search. Therefore, the search module determineswhether input has been received indicating the user has selected theselection mechanism. If the user has initiated the search, then thesearch module generates search results based at least in part on theentered search term(s) in Operation 1330. In addition, in someembodiments, the user may indicate other criteria for conducting thesearch.

For example, the search window may include a field that allows the userto identify applicability requirements for the search results.Applicability generally pertains to the context for which the results(e.g., information found in topics) are valid. The context can beassociated with a physical configuration of the item, but can alsoinclude other aspects such as support equipment availability and/orenvironmental conditions. In addition, the search window may include afield that allows the user to identify the type of content required forthe search results. The content generally pertains to the technicalinformation provided by the search result. For example, different typesof content may include procedural, process, wiring, maintenance,learning, parts, checklists, and/or the like. Further, the search windowmay include other mechanisms that allow the user to identify criteriafor filtering the search results such as information code.

Accordingly, in various embodiments, the search module is configured tosearch different features of the elements found in the table of contentsto identify the search results. For instance, in particular embodiments;the search window is configured to provide the search results withrespect to table of contents, data module, and part name and/or number.Here, the search module searches the table of contents to identify thosetopics with the search term(s) in the title of the topic. In addition,the search module searches the various data (e.g., data modules) thatmake up the technical documentation to identify data in which the searchterm(s) are found in the textual information for the data. Further, thesearch module searches the part names and/or numbers of the parts usedin the item to identify those parts with the search term(s) in the partnames and/or numbers.

Accordingly, in these particular embodiments, the search module mayformat the search results with respect to table of contents, datamodules, and parts (e.g., part names and/or numbers) in Operation 1335.The search module may then provide the search results for displaying inOperation 1340. Here, the search window may be configured to show thesearch results with respect to the three different basis: table ofcontents; data modules; and parts. For example, the search window mayprovide a view pane with a tab for each basis that the user may selectto view the search results for the basis.

At this point, the search module determines whether input has beenreceived indicating the user wishes to exit the search window inOperation 1345. For example, the user may select one of the searchresults (e.g., a topic) to view or the user may simply select amechanism to exit the search window. If so, then the search moduleexits.

It is noted that in some embodiments, the search results are notnecessarily lost (e.g., closed) as a result of the user exiting thesearch window. Instead, the results may be maintained while the user isstill actively signed into the IETM. Such functionality allows for theuser to later return to his or her search results to further view anduse accordingly. For example, the user may initially view a data modulelisted in the search results and then later decided to view the searchresults again because the data module did not have the information theuser was looking for. Therefore, the search results may be maintained sothat the user can later return to them if desired. In some instances,the IETM may be configured to save the search results even past theuser's current sign-in to the IETM.

Predictions Module

Turning now to FIG. 14 , additional details are provided regarding aprocess flow for providing predictions based at least in part on searchterm(s) entered by a user according to various embodiments. FIG. 14 is aflow diagram showing a predictions module for performing suchfunctionality according to various embodiments of the disclosure. inparticular embodiments, the predictions module may be invoked by anothermodule to provide predictions such as, for example, the search modulepreviously described. However, with that said, the predictions modulemay not necessarily be invoked by another module and may execute as astand-alone module in other embodiments.

The process flow 1400 begins with the predictions module reading (e.g.,receive input of) the character(s) typed in by the user on the searchwindow in Operation 1410. In various embodiments, a search index ismaintained in the IETM that is constructed from the dataset for thetechnical documentation of the item. Here, the search index provides amapping of characters (e.g., alphanumeric) to various terms found in thetechnical documentation for the item. Therefore, in these embodiments,the predictions module searches the index to identify predictions basedat least in part on the entered character(s) in Operation 1415.

The predictions module then orders the predictions based at least inpart on certain grounds in Operation 1420. As previously discussed, thegrounds for ordering the predictions may differ depending on theembodiments. For example, the predictions module may order thepredictions based at least in part on alphabetically, frequency of use,recent trends, and/or the like. The predictions module provides of thetop predictions in operation 1425, For instance, the predictions modulemay be configured to provide the top five, ten, and/or the likepredictions that are selectable by the user to automatically completethe search terms in the freeform field provided on the search window.

At this point, the predictions module determines whether input has beenreceived indicating the user has selected a prediction in Operation1430. If not, then the predictions module returns to Operation 1410 toread any further characters entered by the user in the freeform fieldand to make further predictions accordingly. Once the user selects oneof the predictions or finishes typing in characters in the freeformfield, then the predictions module exits.

FIG. 15A provides an example of a search window 1500 displaying searchresults according to various embodiments. In this example, the searchresults are being displayed on a view pane 1510 with respect to datamodules that have content containing the search term “assembly” 1515.Note that view panes 1520, 1525 are also provided for the table ofcontents and part numbers that are hidden on the window 1500 behind thedata module view pane 1515. Turning now to FIG. 15B, the search resultsare now shown as filtered based information code 1530. Here, the userhas selected a mechanism 1535 provided on the search window 1500indicating to filter the results based on information code. In addition,a separate tab 1540, 1545, 1550 is provided for each of table ofcontents pane 1520, data modules pane 1510, and parts pane 1525,respectively, to provide the user with access to the search results forthe three different basis.

Generate List of Parts Module

A list of parts for an item may be provided in the IETM in variousembodiments. In these particular embodiments, this list of parts may begenerated based at least in part on information/data provided in apublication of the technical documentation of the item. Specifically,the list of parts may be generated based at least in part on theillustrated parts breakdown (IPB) found in the publication. Thus, invarious embodiments, a list of parts used by the item may be generatedwithout the need to gather such a list from the suppliers of the partsor any other third-party source outside the publication of the technicaldocumentation for the item.

Turning now to FIG. 16 , additional details are provided regarding aprocess flow for generating a list of parts for the item according tovarious embodiments. FIG. 16 is a flow diagram showing a generate listof parts module for performing such functionality according to variousembodiments of the disclosure. Accordingly, the generate list of partsmodule may be executed in particular embodiments by an entity such asthe management computing entity 100 and/or a user computing entity 110engaged in importing a publication of the technical documentation for anitem.

The process flow 1600 begins with the generate list of parts modulereading the IPB provided with the publication in Operation 1610. Here,the IPB identifies the parts found in the technical documentation forwhich one or more illustrations (e.g., graphics and/or other mediaobjects) are included in the technical documentation. For example, adata module for a particular maintenance task may be found in thepublication for the technical documentation that references a particularpart used in a repair that is detailed in the maintenance task.Accordingly, one or more illustrations of installing the part may beincluded along with the data module that can be displayed to a user asthe user views the maintenance task via the IETM. Therefore, a referenceto the one or more illustrations may be provided in the IPB.

Thus, the generate list of parts module identifies the parts (e.g., partnames and/or numbers) found in the IPB in Operation 1615 and generatesthe list of parts based at least in part on the parts found in the IPBin Operation 1620. Accordingly, as detailed further herein, thegenerated lists of parts may then be viewed by a user via the IETM.

List of Parts Module

Accordingly, a user may request to view the list of parts for an itemvia the IETM. For example, a selection mechanism may be provided such asa button provided on a toolbar to allow the user to request to view thelist of parts for the item. As a result, a window may be provided fordisplaying the list of parts. Accordingly, in particular embodiments,the window may be configured similar to the other windows mentionedherein.

For instance, in some embodiments, the window may be configured to havea first view pane displaying the list of parts and a second view panethat is used to display various information on a part found in the listsof parts. The window may be configured to display the view panes onnon-overlapping portions of the window. In addition, each part displayedin the list of parts may be selectable (e.g., may be displayed as ahyperlink and/or displayed with one or more selections mechanisms suchas buttons) to provided information on the part. In some embodiments,such information may be displayed on a view pane (e.g., the second viewpane) and/or may be displayed on a separate window. As now furtherdetailed, the window may provide the user with various functionalitythat may be used with respect to the list of parts.

Turning now to FIG. 17 , additional details are provided regarding aprocess flow for providing functionality for the list of parts accordingto various embodiments. FIG. 17 is a flow diagram showing a list ofparts module for performing such functionality according to variousembodiments of the disclosure. Accordingly, the list of parts module maybe executed in particular embodiments as a result of a user who isviewing the list of parts via the IETM invoking various functionality.

The process flow 1700 begins with the list of parts module determiningwhether input has been received indicating a selection of a part by theuser in Operation 1710. As noted, in particular embodiments, each partin the list of parts may be selectable. For example, each part in thelist of parts may be displayed as a hyperlink and/or along with sometype of selection mechanism (e.g., a button) to allow the user to selectthe part from the list. Accordingly, in response to determining the userhas selected a part, the list of parts module provides media content forthe part in Operation 1715.

As previously noted, the media content may be made up of one or moreillustrations that may include 2D and/or 3D graphics, as well as othermedia objects such as images and/or videos that may be provided in thetechnical documentation for the item. Therefore, in particularembodiments, the list of parts module may be configured to retrieve themedia content and provide the list of parts for display on a first viewpane of the window and the media content for the selected part on asecond view pane of the window. As noted, the window may be configuredso that the first and second view panes are displayed on non-overlappingportions of the window. In addition, in particular embodiments, the partmay be highlighted in the media content so that the user can easilyidentify it in the content.

Further, the selected part may be displayed in the list of parts using aformat to demonstrate the part has been selected such as, for example,the selected part may be highlighted, shown in a particular color, shownwith a border, and/or the like. Furthermore, functionality may beprovided for the selected part such as, for example, a selectionmechanism that provides functionality to allow the user to order thepart from the IETM.

If the user has not selected a part in the list of parts, then the listof parts module determines whether input has been received indicatingthe user has identified one or more level indicators for relisting thelist of parts in Operation 1720. As previously noted, each of the partsmay be associated with one or more components of the item for which thetechnical documentation is being viewed by the user via the IETM. Invarious embodiments, each of these components may be identified with afunctional and/or physical structure of the item such as assembly,sub-assembly, sub-sub-assembly, system, sub-system, sub-sub-system,subject, unit, part, and/or the like. Therefore, the user may beinterested in viewing the parts in the list of parts broken down intothese levels of functional and/or physical structure. If that is thecase, then the list of parts module relists the list of parts based atleast in part on the levels identified (e.g., selected) by the user andprovides the relisted list of parts for display on the window inOperation 1725.

Accordingly, each of the parts in the list of parts may display variousinformation for the part that may be selectable to retrieve and viewsearch results on additional information found in the technicaldocumentation for the part. For instance, each of the parts may displaya part name and/or number for the part that is selectable (e.g., that isdisplayed as a hyperlink and/or along with a selection mechanism such asa button) that when selected by the user, a preview is generated anddisplayed providing results on textual information and/or media content(e.g., illustrations and/or other media objects) found in the technicaldocumentation for the selected part.

For example, the user may use a mouse to click on, right click on, orhover over a part in the list of parts or use a stylus or finger toselect a part in the list of parts to generate a preview for the part.Therefore, the list of parts module determines whether input has beenreceived indicating the user has selected a part name and/or number fora part to generate a preview in Operation 1730. If so, then the list ofparts module generates a preview of results based at least in part oninformation on the part found in the technical documentation for theitem in Operation 1735 and provides the preview for display in Operation1740.

In particular embodiments, the part preview may be provided as aseparate window. For instance, in some embodiments, the preview windowmay be superposed over a portion of the window displaying the list ofparts. Accordingly, the part preview may provide the user withinformation/data, tables, instructions, illustrations, other mediacontent, links to additional and/or related information, and/or the likeassociated with the selected part. In some embodiments, the part previewis configured to provide only a preview of some of the content found inthe technical documentation on the part. 111 addition, variouscomponents of the results may be selectable to access furtherinformation.

Although not specifically shown in FIG. 17 , other information may beretrieved and displayed in a preview for the part in some embodiments.Specifically, each of the parts in the list of parts may be associatedwith one or more commercial and government entity (CAGE) codes and/orone or more source, maintenance, and recovery (SMR) codes. In general,these codes identifier a supplier for the part, although other types ofsupplier identifiers may be used. In particular embodiments, these codesmay be displayed along with each part in the list of parts on thewindow. In addition, each of these codes may be selectable on the window(e.g., displayed as a hyperlink and/or associated with a selectionmechanism) to allow the user to view a preview displaying information onthe particular supplier associated with the code. For example, the usermay use a mouse to click on, right click on, or hover over a code for apart or use a stylus or finger to select a code for a part to generate apreview. Therefore, the list of parts module may determine whether inputhas been received indicating the user has selected a CAGE or SMR codefor a part. If so, then the list of parts module generates a preview forthe supplier associated with the selected CAGE or SMR code and providesthe preview for the user to view.

Similar to the part preview, the supplier preview may be provided as aseparate window. For instance, in some embodiments, the preview windowmay be superposed over a portion of the window displaying the list ofparts. Accordingly, the supplier preview may provide the user withinformation/data, tables, instructions, illustrations, other mediacontent, links to additional and/or related information, and/or the likeassociated with the supplier. In some embodiments, the supplier previewis configured to provide only a preview of some of the content found inthe technical documentation on the supplier. In addition, variouscomponents display on the preview may be selectable to access furtherinformation.

Similarly, related maintenance procedures and/or tasks that mention thepart may be provided for each part in the lists of parts that areselectable. For example, the user may use a mouse to click on, lightclick on, or hover over a maintenance procedure and/or task for a partor use a stylus or finger to select a maintenance procedure and/or taskfor a part to generate a preview. Therefore, the list of parts modulemay determine whether input has been received indicating the user hasselected a maintenance procedure and/or task related a part. If so, thenthe list of parts module generates a preview for the related maintenanceprocedure and/or tasks and provides the preview for the user to view.

Again, similar to the part and supplier previews, the maintenanceprocedure and/or task preview may be provided as a separate window. Forinstance, in some embodiments, the preview window may be superposed overa portion of the window displaying the list of parts. Accordingly, themaintenance procedure and/or task preview may provide the user withinformation/data, tables, instructions, illustrations, other mediacontent, links to additional and/or related information, and/or the likeassociated with the maintenance procedure and/or task. In someembodiments, the preview is configured to provide only a preview of someof the content found in the technical documentation on the maintenanceprocedure and/or task. In addition, various components display on thepreview may be selectable to access further information.

Further, as previously noted, functionality may be provided in someembodiments that allows the user to order a selected part from the IETM.As discussed further herein, this functionality provides an order formthat can then be populated and submitted by the user to order the part.Therefore, in these particular embodiments, the list of parts moduledetermines whether input has been received indicating the user wouldlike to order a selected part in Operation 1745. If so, then the list ofparts module enables the order part functionality in Operation 1750.

Finally, in particular embodiments, the list of parts module may providefunctionality to allow the user to view other items besides the item theuser is currently viewing the technical documentation for that also usea selected part in the list of parts. Here, a mechanism may be displayedalong with the selected part that can be used to display a list of otheritems that also use the part. For example, a selectable plus sign may beprovide that the user may use a mouse to click on, right click on, hoverover, and/or the like to display the list of other items that also usethe part.

Therefore, in these particular embodiments, the list of parts moduledetermines whether input has been received indicating the user wouldlike to view the list of other items that use a selected part inOperation 1755. If so, then the list of parts module generates a previewdisplaying the list of other items that use the selected part inOperation 1760 and provides the preview for the user to view inOperation 1765.

Again, the preview may be provided as a separate window. For instance,in some embodiments, the preview window may be superposed over a portionof the window displaying the list of parts. Accordingly, the preview mayprovide the user with information/data, tables, instructions,illustrations, other media content, links to additional and/or relatedinformation, and/or the like associated with the list of other items. Insome embodiments, the preview is configured to provide only a preview ofsome of the content found in the technical documentation on the list ofother items. In addition, various components display on the preview maybe selectable to access further information.

Accordingly, such a list of items may be quite helpful to the user undercertain circumstances. For example, the user may be maintenancepersonnel who is tasked with performing certain maintenance on an objectsuch as an aircraft. Therefore, the user may have signed into the IETMto view the technical information for the type of aircraft.Specifically, the user may have signed into the IETM to viewdocumentation on the maintenance task he or she is to perform on theaircraft. The documentation on the maintenance task may identify aparticular part needed in performing the task. However, the user maydetermine that the particular part is not currently in stock. Therefore,in this instance, the user may view the list of parts, select theparticular part in the list, and generate and display the previewshowing other types of aircraft that also use the particular part. As aresult, the user may be able e to obtain the part from inventory foranother type of aircraft and/or may be able to use the part from anotheraircraft to perform the maintenance task instead of waiting for the partto be ordered and received.

FIG. 18A provides an example of a window 1800 displaying a list of partsaccording to various embodiments. In this example, the window 1800provides a first view pane 1810 displaying the list of parts for aparticular item (e.g., platform 1810) in which a particular part 1815found on the list has been selected. As a result, the window 1800 inthis example provides a second view pane 1820 displaying an illustrationwith the selected part 1825 highlighted in the illustration. Further, amechanism is provided for displaying a window 1830 providingfunctionality to perform with respect to the selected part 1825 such asordering the part 1825.

Turning now to FIG. 18B, an example of a mechanism 1835 that can be usedby a user in various embodiments in selecting identifiers for levels forrelisting the list of parts is demonstrated. Here, the mechanism 1835 isprovided as a dropdown menu control that allows the user to relist thelist of parts according to part associated with an end item, component,major assembly, assembly, and/or subassembly. For instance, in thisexample, the user has indicated to relist the list of parts according toassembly 1840, but not according to subassembly 1845.

Finally, FIG. 18C provides an example of a preview 1850 displaying theinformation for a supplier as a result of the user selecting a CAGE codeassociated with a part in the list of parts according to variousembodiments. Likewise, FIG. 18D provides an example of a preview 1850displaying a list of other items that use a selected part according tovarious embodiments.

Order Part Module

As previously noted, various embodiments provide functionality to allowa user to order a part from the IETM. Turning now to FIG. 19 ,additional details are provided regarding a process flow for ordering apart from the IETM according to various embodiments. FIG. 19 is a flowdiagram showing an order part module for performing such functionalityaccording to various embodiments of the disclosure. In particularembodiments, the order part module may be invoked by another module toorder a part from the IETM such as, for example, the list of partsmodule previously described. For instance, a user may select a mechanism(e.g., button) provided for a selected part on a window displaying thelist of parts and as a result, the list of parts module may invoke theorder part module. However, with that said, the order part module maynot necessarily be invoked by another module and may execute as astand-alone module in other embodiments.

The process flow 1900 begins with the order part module reading the partnumber for the part in Operation 1910. Here, for example, the partnumber may be provided to the order part module from another module suchas the list of parts module. While in other instances, the order partmodule may read the part number (e.g., provided as input) from some typeof window being displayed. The part number serves as an identifier forthe part. Therefore, depending on the embodiment, the part number may bein various forms such as, for example, an alphanumeric, and may includecharacters such as dashes, underscore, ampersand, commercial at sign,and/or the like. Those of ordinary skill in the art can envision othercharacters and/or symbols that may be used in a part number in light ofthis disclosure.

The order part module then identifies a system for the item for whichthe part will be used in Operation 1915. Accordingly, the item isgenerally the item related to the technical documentation currentlybeing viewed by the user through the IETM. However, in some embodiments,the user may identify a specific item that is not necessarily the itemassociated with the technical documentation currently active for theIETM.

Regardless, many of the items may be associated with a backend systemthat is used in managing the item. For example, the item may involve atype of aircraft used by the military. Here, the military's backendsystem used in managing the individual aircraft for the type of aircraftmay normally be used in ordering parts for the aircraft. This backendsystem may have a specific electronic form that is used in orderingparts for the aircraft. Accordingly, forms for the different systems maybe available in the IETM and the order part module selects theappropriate form based at least in part on the system associated withthe item in Operation 1920.

The order part number then queries a stock number for the part inOperation 1925. The stock number is often used in identifying thephysical location where a particular part is stored in a warehouseand/or inventory. Similar to a part number, the stock number serves asan identifier and may be in various forms such as, for example, analphanumeric, and may include characters such as dashes, underscore,ampersand, commercial at sign, and/or the like. Those of ordinary skillin the art can envision other characters and/or symbols that may be usedin a stock number in light of this disclosure. In particularembodiments, the order part module may be configured to identify a stocknumber for a particular supplier of the part based at least in part onthe part number. For example, the supplier may be identified based atleast in part on a CAGE and/or SMR code associated with the part foundin the technical documentation for the item, although other identifiersmay be used for the supplier. Accordingly, in particular embodiments,the order part module determines whether a stock number can be found forthe part in Operation 1930. If not, then the order part module mayprovide an error message to the user in Operation 1935 informing theuser that a valid stock number cannot be located for the part.

If a valid stock number is located for the part, then the order partmodule queries data (e.g., information) for the part in Operation 1940.In particular embodiments, the IETM may be in communication with thesupplier's system over some type of network so that the data on the partcan be queried directly from the supplier. In other embodiments, theIETM may store the data internally and the order part module queries thedata accordingly.

Once the order part module has queried the data for the part, the moduleauto-populates one or more of the fields on the electronic order formbased at least in part on the queried data in Operation 1945. At thispoint, the order part module provides the electronic order form fordisplay for the user to view in Operation 1950. Here, in particularembodiments, the form may be displayed on a separate window than thewindow displaying the list of parts. The user may then provide anyadditional data (e.g., information) that may be needed on the electronicform such as, for example, a quantity of the part that is to be ordered.Once the user has completed filling out the electronic form, the usermay submit the electronic form. For example, the electronic order formmay provide a selection mechanism (e.g., a button) that the user canselect to submit the order for the part. Accordingly, the form may besubmitted directly to the supplier to fulfill the order for the part orthe form may be placed in a queue and submitted indirectly depending onthe embodiment. Other options may be provided to the user in someembodiments as discussed further herein.

Finally, the order part module determines whether input has beenreceived indicating to exit in Operation 1955. If not, then the orderpart module continues to display the electronic order form. Otherwiseonce the user has completed submitting the order for the part, or wishesto simply exit the form and indicated such, the order part module exits.

Submit Order for Part Module

Turning now to FIG. 20 , additional details are provided regarding aprocess flow for submitting an order for a part from the IETM accordingto various embodiments. FIG. 20 is a flow diagram showing a submit orderfor part module for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the submitorder for part module may be invoked by another module to submit theorder for the part from the IETM such as, for example, the order partmodule previously described. For instance, a user may select a mechanism(e.g., button) provided on an electronic order form and as a result, theorder part module may invoke the submit order for part module. However,with that said, the submit order for part module may not necessarily beinvoked by another module and may execute as a stand-alone module inother embodiments.

As previously noted, the user may be provided various options forsubmitting the order for the part depending on the embodiment. Some ofthese options may be contingent on whether or not the user's computerentity 110 is currently in communication with another system. Forexample, the user may be working out in the field using the IETM toperform maintenance where a connectively (e.g., a wireless network) isnot available. As a result, the user may need to order a replacement fora part that was used during the maintenance repair. However, the usercannot submit the order for the part directly to the supplier since theuser's computing entity 110 is unable to communicate with the supplier'ssystem. While in other instances, the computing entity 110 may not be incommunication with any other system for security reasons.

Therefore, the process flow 2000 begins with the submit order for partmodule reading (e.g., receiving input) the user's selection forsubmitting the order for the part in Operation 2010. As noted, theoptions available to the user may be dictated based at least in part onwhether or not the user's computing entity 110 is currently incommunication with any other systems. Here, the different options may bemade available to the user on the electronic order form as one or moreselection mechanisms (e.g., one or more buttons). Further, the selectionmechanisms may be made available on the electronic order form based atleast in part on the options currently available to the user.

One such option that may be used in various embodiments is to submit theorder for the part directly to the supplier. Depending on theembodiment, this option may involve the user's computing entity 110submitting the order for the part directly to the supplier's system ormay involve sending the order for the part initially to someintermediary who then submits the order to the supplier. Therefore, thesubmit order for part module determines whether input has been receivedindicating the user has selected the submit order option in Operation2015. If the submit order for part module determines the user hasselected this option, then the submit order for part module submits theorder to a remote system in Operation 2020. Accordingly, the remotesystem may be associated with the supplier of the part or to anintermediary. For example, the submit order for part module may beconfigured to submit the order to a procurement system for an airline ininstances in which the user is a maintenance employee of the airline whois ordering a replacement part for an aircraft. In turn, the procurementsystem may process the order for the part and then submit it to thesupplier to fulfill.

In addition, the submit order for part module may submit the order tothe remote system using different procedures depending on theembodiment. For example, in one embodiment, the order may be submittedvia electronic data interchange (EDI) between the user's computingentity 110 and the supplier's or intermediary's system. In anotherembodiment, the order may be submitted via a message such as an email,instant messaging, text messaging, and/or the like. Those of ordinaryskill in the art can envision other procedures that may be used insubmitting the order to the remote system in light of this disclosure.

Another option that may be used in various embodiments is to place theorder in a queue (e.g., a shopping cart) and submit the order at a latertime. This option may be used when the user's computing entity 110 isnot currently in communication with another system. Therefore, thesubmit order for part module may determine whether input has beenreceived indicating the user has selected to add the order to a shoppingcart option in Operation 2025. If so, then the submit order for partmodule places the order in the shopping cart in Operation 2030. Once theorder has been placed in the shopping cart, the order may then besubmitted at a later time when the user's computing device 110 is incommunication with another system. Accordingly, depending on theembodiment, the order for the part may be submitted to the supplierdirectly or initially to an intermediary using any number of differentprocedures at the later time.

Finally, another option that may be used in various embodiments is tosend the order through another channel of communication. In theseparticular embodiments, the submit order for part module generates agraphical code with the order information and provides the code fordisplay for the user to scan using his or her mobile device. Here, thegraphical code may be provided in various forms such as a barcode, aquick response (QR) code, a one-dimensional code, a universal productcode, a data matric code, and/or the like. As a result, the order can besubmitted using the mobile device's cellular network as a channel ofcommunication, although the mobile device may be connected to othertypes of networks such as WIFI. Depending on the embodiments, the usermay use a generic code reader application on his or her mobile device oran application specifically designed to submit the order. Using aspecific application designed to submit the order may also allow for theorder to be submitted in a secure manner. For example, the user may berequired to enter security information into the application to open theapplication to scan the graphical code.

Therefore, the submit order for part module determines whether input hasbeen received indicating the user has selected the graphical code optionin Operation 2035. If so, then the submit order for part modulegenerates the graphical code in Operation 2040 and provides the code inOperation 2045. For example, in particular embodiments, the graphicalcode may be displayed on a separate window. At this point, the submitorder for part module in some embodiments records the submission of theorder in Operation 2050. Therefore, in these particular embodiments, theIETM can be used a recordkeeper for ordered parts. It noted thatrecordation of the submission of orders placed in the shopping cart maynot be performed in some embodiments until the orders have actually beensubmitted.

FIG. 21A provides an example of a part 2100 that has been selected inwhich the option to order the part (e.g., button) 2110 has been providedto the user via a window according to various embodiments. FIG. 21Bprovides an example of an electronic order form 2115 that has providedon a window as a result of the user exercising the option to order thepart 2110 according to various embodiments. Here, the user has beenprovided the option to directly submit the order for the part (e.g.,button) 2120 and the option to place the order in the shopping cart(e.g., button) 2125. Finally, FIG. 21C provides an example of agraphical code in the form of a QR code 2130 generated according tovarious embodiments that can be scanned by the user to submit an orderfor a part.

Display Topic Module

Turning now to FIG. 22 , additional details are provided regarding aprocess flow for displaying content for a topic found in the technicaldocumentation for an item via an IETM according to various embodiments.FIG. 22 is a flow diagram showing a display topic module for performingsuch functionality according to various embodiments of the disclosure.In particular embodiments, the display topic module may be invoked byanother module to provide a topic for display such as, for example, theTOC module previously described. For instance, a user may select a topicfound in a table of content displayed on a window and as a result, theTOC module may invoke the display topic module. However, with that said,the display topic module may not necessarily be invoked by anothermodule and may execute as a stand-alone module in other embodiments.

As previously noted, topics found in the technical documentation for anitem may include procedures, tasks, operations, services, checklists,planning, and/or the like performed with respect to the item. Forinstance, topics may include maintenance procedures and/or tasksperformed on the item. In addition, topics may include differentcomponents that make up the item.

For example, a user may be viewing the table of contents for thetechnical documentation of the item and may select a maintenanceprocedure listed in the table of contents directly from the table toview the content in the technical documentation on conducting themaintenance procedure. Likewise, the user may be viewing an illustration(e.g., a 2D graphic) of the front braking assembly of an aircraft andmay select the front wheel directly from the illustration to view thecontent on the technical documentation for the front wheel.

In particular embodiments, the technical documentation may be formattedaccording to S1000D standards and therefore, the documentation for aparticular topic may be found in a data module. A data module primarilyincludes two parts, metadata and content. The metadata is made up of anidentification section and a status section. These two sections are usedto control a module's retrieval. The content is what a user views on thetopic. The content typically is made up of textual information, as wellas references (e.g., links) to any media content (e.g., illustrationssuch as 2D and/or 3D graphics, images, audio, videos, and/or the like)and other data pertaining to the topic. The content of the data moduleis usually specific to the type of the data module, which is written inaccordance with that type's schema. The types of content found in a datamodule may include, for example: procedural used for tasks and stepsinformation; fault used for troubleshooting; illustrated parts data usedfor parts lists and other illustrated parts data; process used forsequencing other data modules and/or steps; learning used fortraining-related material; maintenance checklists used for preventivemaintenance, services, and inspections; and/or the like.

Accordingly, the process flow 2200 begins with the display topic moduleretrieving the textual information for the topic in Operation 2210. Insome embodiments, the display topic module creates selectable partsfound in the textual information in Operation 2215. As discussed furtherherein, the parts (e.g., the part names and/or numbers) mentioned in thetextual information are recognized and made selectable by displayingthem as a hyperlink and/or with some other type of selection mechanismsuch as a button. As a result, in these particular embodiments, a userviewing the textual information is able to access specific informationvia the IETM on the part directly from the textual information, as wellas perform other functionality with respect to the part such as orderthe part from the IETM.

In addition to creating selectable parts, the display topic modulecreates selectable applicability found in the textual information inOperation 2220 in some embodiments. Similar to parts, as a result, auser viewing the textual information is able to access specificinformation on applicability mentioned in the textual informationdirectly from the textual information.

Further, the display topic module may lock data found in the textualinformation in Operation 2225. This particular operation may beperformed in some embodiments when the topic selected by the userprovides alerts in the content such as warnings, cautions, notes, and/orthe like. As discussed further herein, the content found after an alertmay be locked (e.g., not able to view and/or not able to scroll through)until the user viewing the content has acknowledged the alert. Thisfunctionality helps to ensure the user is giving the alerts found in thecontent proper attention.

Furthermore, the display topic module may create a securityclassification for the textual information in Operation 2230.Accordingly, the textual information may be configured so that thoseusers with a certain level of security should be able to view thecontent found in the textual information. Therefore, in particularembodiments, the display topic module may set up a securityclassification for the content based at least in part on the user'scredentials who is requesting to view the content. For example, thisoperation may involve marking the content with a particular level ofsecurity (e.g., top secret) and making the content unviewable to theuser.

At this point, the display topic module determines whether the datamodule references any non-textual content in Operation 2235. Here,non-textual content may involve illustrations such as 2D and/or 3Dgraphics and/or other media objects such as images, videos, audios,and/or the like. If so, then the display topic module retrieves one ofthe non-textual contents in Operation 2240. Accordingly, the referenceto the non-textual content found in the data module may provide a link(e.g., html) and/or other information such as an information controlnumber (ICN) to retrieve the non-textual content. In particularembodiments, the display topic module may then create a securityclassification for the non-textual content, similar to the textualinformation, in Operation 2245.

The display topic module then determines whether the data for the topic(e.g., the data module for the topic) references other non-textualcontent (e.g., another illustration or media object) in Operation 2250.If so, then the display topic module returns to Operation 2240,retrieves the next non-textual content referenced in the data module,and creates a security classification for the retrieved non-textualcontent.

Once the display topic module has retrieved all of the non-textualcontent for the topic, the display topic module provides the content forthe topic for display via a window in Operation 2255. As discussedfurther herein, the content may be displayed using a number of differentconfigurations depending on the embodiment. For example, the displaytopic module may be configured to display the content on multiple viewpanes so that multiple aspects of the content (e.g., textual informationand illustrations) can be viewed by the user at the same time.Accordingly, in particular embodiments, the window displaying thecontent may be configured so that the view panes are displayed onnon-overlapping portions of the window.

In various embodiments, the display topic module may invoke variousmodules to perform some of the operations just described. Accordingly, adiscussion of these various modules is now provided.

Selectable Parts Module

Turning now to FIG. 23 , additional details are provided regarding aprocess flow for causing parts found in textual information to bedisplayed as selectable according to various embodiments. FIG. 23 is aflow diagram showing a selectable parts module for performing suchfunctionality according to various embodiments of the disclosure. Inparticular embodiments, the selectable parts module may be invoked byanother module to cause the parts to be displayed as selectable such as,for example, the display topic module previously described. However,with that said, the selectable parts module may not necessarily beinvoked by another module and may execute as a stand-alone module inother embodiments.

The process flow 2300 begins with the selectable parts module selectinga part from the list of parts in Operation 2310. As previouslydiscussed, a list of parts may be generated in various embodiments fromthe illustrated parts breakdown found in a publication of the technicaldocumentation for the item during a time when the publication is beingimported into the IETM. Accordingly, this list of parts may identify theinformation associated with each part found in the list such as, forexample, illustrations of components of the item displaying the part andprocesses, procedures, maintenance, and/or the like that make use of thepart.

The selectable parts module then searches the textual information for atopic (e.g., the data module for a topic) to identify occurrences of thepart in the textual information in Operation 2315. Here, for instance,the part may be identified in the textual information by a name and/orpart number. Therefore, in particular embodiments, the selectable partsmodule may be configured to perform some type of character recognitionto identify occurrences of the part in the textual information.

Accordingly, the selectable parts module determines whether anoccurrences of the part have been found in the textual information inOperation 2320. If so, then the selectable parts module configures eachof the occurrences in the text information as selectable in Operation2325. Depending on the embodiments, the selectable parts module may makethe part selectable in the textual information using a number ofdifferent mechanisms. For instance, the selectable parts module maydisplay the part (e.g., the part name and/or number) in the textualinformation as a hyperlink. In other instances, the selectable partsmodule may display the part along with a selection mechanism in thetextual information such as a button.

Further, the selectable parts module may configure the part so thatmultiple types of selection may be used by a user in some embodiments.For example, the selectable parts module may configure the part so thata user can hover his or her mouse over the part (e.g., the part nameand/or number) to view a preview providing preview information on thepart and click on the part to display content (e.g., textualinformation, as well as media content such as illustrations) for thepart on a window. Furthermore, various functionality may be provided asa result of a user selecting the part in the textual information suchas, for example, functionality to enable the user to order the part fromthe IETM and/or functionality to allow the user to view other items thatuse the part. Those of ordinary skill in the art can envision othermechanisms, configurations, and functionality that may be implementedfor the parts in light of this disclosure.

At this point, the selectable parts module determines whether anotherpart is found on the list of parts in Operation 2330. If so, then theselectable parts module returns to Operation 2310, selects the next partfound on the list of parts, and repeats the operations just describedfor the newly selected part. Once the selectable parts module hasprocessed all the parts found on the list of parts, the module exits.

Selectable Applicability Module

Turning now to FIG. 24 , additional details are provided regarding aprocess flow for causing applicability found in textual information tobe displayed as selectable according to various embodiments. FIG. 24 isa flow diagram showing a selectable applicability module for performingsuch functionality according to various embodiments of the disclosure.In particular embodiments, the selectable applicability module may beinvoked by another module to cause applicability to be displayed asselectable such as, for example, the display topic module previouslydescribed. However, with that said, the selectable applicability modulemay not necessarily be invoked by another module and may execute as astand-alone module in other embodiments.

As previously noted, applicability generally pertains to the context forwhich the information for a topic is valid. The context can beassociated with a physical configuration of an item, but can alsoinclude other aspects such as support equipment availability and/orenvironmental conditions. For example, a user may be viewing informationon the first wheel assembly for an aircraft. Accordingly, theinformation may provide information for both an air brake configurationof the assembly and a disc brake configuration of the assembly. However,the user may be specifically working on an aircraft at the time withdisc brakes. Therefore, the information being viewed in on the frontwheel assembly pertaining to disc brakes is applicable while theinformation pertaining to air brakes is not.

Also previously noted, the IETM may be configured in various embodimentsto allow the user to sign into the IETM to view the technicaldocumentation for an item with respect to a specific object (e.g., aspecific aircraft in an airline's fleet or a specific aircraftconfiguration) or a universal object. For example, a user may beconducting training on performing maintenance on a specific model ofaircraft and therefore signs into the IETM using a universal object sothat he or she can view technical documentation on the model of aircraftusing either an air brake configuration or a disc brake configuration.

Therefore, in particular embodiments, the process flow 2400 begins withthe selectable applicability module determining whether the user issigned into the IETM with respect to a specific object or a universalobject for the item in Operation 2410. The reason for making such adetermination in these embodiments is the selectable applicabilitymodule may be configured to only make those occurrences of applicabilityfound in the textual information selectable that are actually applicableto the current instance of the user signed into the IETM. Therefore,returning to the example, if the user is signed into the IETM to viewtechnical documentation on a specific model of aircraft and the user hassigned in identifying a specific object with an air brake configuration,then the selectable applicability module does not make any of theoccurrences of applicability involving disc brakes selectable in thetextual information.

Thus, if the user is signed into the IETM with respect to a specificobject of the item, then the selectable applicability module generatesonly those occurrences of applicability related to the specific objectfound in the textual information as selectable in Operation 2415.However, if the user is signed into the IETM with respect to a universalobject of the item, then the selectable applicability module generatesall of the occurrences of applicability found in the textual informationas selectable in Operation 2420.

Similar to the selectable parts module, the selectable applicabilitymodule may be configured in particular embodiments to perform some typeof character recognition to identify occurrences of applicability in thetextual information. In addition, the selectable applicability modulemay make an occurrence of applicability selectable in the textualinformation using a number of different mechanisms. Further, theselectable applicability module may configure an occurrence ofapplicability so that multiple types of selection may be used by a userin some embodiments. Furthermore, the selectable applicability modulemay provide various functionality for an occurrence of applicability asa result of a user selecting the occurrence in the textual information.Those of ordinary skill in the art can envision various mechanisms,configurations, and functionality that may be implemented forapplicability in light of this disclosure.

Lock Content Module

Turning now to FIG. 25 , additional details are provided regarding aprocess flow for locking content for a topic according to variousembodiments. FIG. 25 is a flow diagram showing a lock content module forperforming such functionality according to various embodiments of thedisclosure. In particular embodiments, the lock content module may beinvoked by another module to lock content for a topic such as, forexample, the display topic module previously described. However, withthat said, the lock content module may not necessarily be invoked byanother module and may execute as a stand-alone module in otherembodiments.

As previously discussed, the textual information for a topic may includeelement types providing various alerts. For example, the textualinformation may provide a warning alerting a user of possible hazardsassociated with a material, a process, a procedure, and/or the like. Inaddition, the textual information may provide a caution alerting theuser that damage to a material is possible if instructions in anoperational and/or procedural task are not followed precisely. Inparticular embodiments, such alerts are tagged in the textualinformation of the data (e.g., data module) for the topic found in thetechnical documentation.

Thus, the process flow 2500 begins with the lock content module readingthe textual information for the topic in Operation 2510. Accordingly,the lock content module determines whether a tag for an alert has beenencountered in the textual information in Operation 2515. If so, thenthe lock content module records a marker for the tag in Operation 2520.Here, the marker identifies where in the textual information the tag isfound. As discussed herein, the marker enables the lock content moduleto lock the portion of the content found in the textual informationassociated with the alert. The lock content module then determineswhether additional textual information remains after the occurrence ofthe alert in Operation 2525. If so, then the lock content module returnsto Operation 2510 and continues reading the textual information toidentify further occurrences of tags for alerts in the information.

Once the lock content module has read the entire textual information forthe topic and has recorded markers for all of the tags for alerts, thelock content module selects a marker for a tag in Operation 2530. Thelock content module then identifies the preceding marker for a tag inOperation 2535. It is noted that the lock content module may beconfigured in particular embodiments to skip the first marker of a tagfound in the textual information since this marker/tag would not have apreceding marker/tag found in the textual information. At this point,the lock content module locks the portion of the content found betweenthe tags for the two markers in the textual information in Operation2540.

Depending on the embodiment, the lock content module may be configuredto lock the portion of the content using a number of differentapproaches and/or any combination thereof. For instance, the lockcontent module may obscure a user's ability to view the portion of thecontent in some embodiments. For example, the lock content module maygrey out the portion of the content so that it cannot be read. In someembodiments, the lock content module may disable any interactivefunctionality found within the portion of the content. For example, theportion of the content may contain an occurrence of a selectable part.Here, the lock content module may disable the selectable functionalityof the selectable part. In some embodiments, the lock content module maylock the user's ability to scroll through the portion of the contentdisplayed on the window. Those of ordinary skill in the art can envisionother approaches that may be used in locking the portion of the contentin light of this disclosure.

Once the lock content module has locked the portion of the content, themodule determines whether a marker for another tag exists in Operation2545. If so, then the lock content module returns to Operation 2530,selects the next marker, and preforms the operations just discussed tolock the portion of the content in the textual information accordingly.Once the lock content module has processed all the markers, the moduleexits.

Security Classification Module

Turning now to FIG. 26 , additional details are provided regarding aprocess flow for setting a security classification for specific contentof a topic according to various embodiments. FIG. 26 is a flow diagramshowing a security classification module for performing suchfunctionality according to various embodiments of the disclosure. Inparticular embodiments, the security classification module may beinvoked by another module to set the security classification for contentsuch as, for example, the display topic module previously described.However, with that said, the security classification module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

In various embodiments, the metadata for a topic (e.g., the data modulefor the topic) may include a security classification tag (e.g., a code)that identifies a level of security with respect to the content for thetopic. This may also be true with respect media content for the topicsuch as illustrations, videos, audio, and/or other data associated withthe topic. Therefore, when displaying the various components of contentfor the topic on a window, the security classification tag found in themetadata for a particular component of content can be used to setformatting and properties for the content.

Thus, the process flow 2600 begins with the security classificationmodule reading the security classification tag for a textual or anon-textual component of content for the topic in Operation 2610. Thesecurity classification module then reads the credentials for the userin Operation 2615. Accordingly, in particular embodiments, theformatting and/or properties associated with the content may becontingent based on the user's level of security. For example, if theuser has a high level of security (e.g., a top secret clearance), thenthe user may be able to view content that may not normally be availablefor viewing by many other users. Here, the credentials used by the userin signing into the IETM may be used to identify the user's level ofsecurity.

Next, the security classification module in some embodiments formats aborder for the content based at least in part on the securityclassification of the content in Operation 2620. For instance, thesecurity classification that may be set for the content may includeunclassified, classified, secret, top secret, and/or the like. Here, thesecurity classification module may format a border placed around thecontent as it is displayed on a window based at least in part on thesecurity classification set for the content. For example, the contentmay be displayed on the window in a view pane. Therefore, in thisexample, the security classification module may format a border placedaround the view pane by including a title in the border identifying thesecurity classification for the content and displaying the border in aparticular color. Such formatting may help the user to quickly identifythe security classification associated with the different components ofcontent being displayed for the topic on the window.

In addition, the security classification module in some embodiments setsthe accessibility of the content based at least in part on the securityclassification of the content and the user's credentials in Operation2625. Specifically, the security classification module sets theaccessibility of the content as it is displayed on the window based atleast in part on the level of security identified in the securityclassification tag for the content and the level of security identifiedin the user's credentials used to sign into the IETM. For example, ifthe level of security identified in the security classification tag forthe content is top secret and the level of security identified in theuser's credential is unclassified, then the security classificationmodule may set the content so that it is not accessible on the window.In this instance, the security classification module may make thecontent unviewable on the window to the user. The securityclassification module may also disable functionality for the contentsuch as, for example, disabling the user's ability to print the content,copy the content, email the content, and/or the like.

In particular embodiments, the security classification module may beconfigured to also set the accessibility for various interactivefunctionality found in the content. For example, the content may includea part (e.g., a part number and/or name) that is normally selectable toaccess information on the part. In this example, the securityclassification module may have set the accessibility for the content toallow the user to view the content on the window. Specifically, thesecurity classification module may have determined the level of securityfor the content is unclassified and the user's level of security isclassified and as a result, set the accessibility for the content toallow the user to view the content.

In some embodiments, the security classification module may also read aclassification tag for the selectable part in Operation 2630. Here, thesecurity classification module may read the classification tag found inthe metadata for data (e.g., the data module) found in the technicaldocumentation for the part. In this example, the classification tag mayidentify the level of security set for the part is top secret.Therefore, as a result, the security classification module may disablethe user's ability to select the part in the content in Operation 2635.The security classification module may then determine whether anyfurther interactive functionality is found in the content in Operation2640. If so, then the security classification module may perform theoperations just described for the additional functionality.

It is noted that the security classification module may be configured inparticular embodiments to set the formatting and/or functionality ofcontent of various topics with respect to other features and/or displaysthat are provided via the IETM. For instance, the securityclassification module may also be configured to set the accessibility oftopics found in a table of contents for the technical documentation foran item based at least in part on the security classification set forthe topics. Those of ordinary skill in the art can envision otherapplications of setting security classification formatting and/orfunctionality of content in light of this disclosure.

FIG. 27 provides an example of security classification formatting andfunctionality set for the display of a topic according to variousembodiments. In this example, a border 2700 has been placed around aview pane displaying content for the topic on a window. Here, the border2700 includes a title indicating the content (e.g., textual information)for the topic is secret. In addition, the steps found in the textualinformation 2710 have been removed from being able to be viewed by theuser. However, an illustration is also displayed in a view pane on thewindow that is viewable to the user. The border for the illustration2715 indicates the illustration is unclassified and therefore the useris able to view it. Thus, the example demonstrates how the formattingand functionality of various sections of content for a topic may be setdifferently based at least in part on the security classificationsidentified for the various sections of content.

Topic Module

Turning now to FIGS. 28A and 28B, additional details are providedregarding a process flow for invoking functionality for a topicdisplayed on a window according to various embodiments. FIGS. 28A and28B are a flow diagram showing a topic module for performing suchfunctionality according to various embodiments of the disclosure.Accordingly, the topic module may be executed by an entity such as themanagement computing entity 100 and/or the user computing entity 110previously discussed. In various embodiments, the topic module isexecuted once a user has selected a topic to view and the topic isdisplayed to the user on a window. As previously noted, the window maybe displaying using a various of configurations depending theembodiment. For example, the window may display multiple pane thatprovide various content for the topic. Once displayed, the user maydecide to invoke different interactive functionality provided for thetopic.

Therefore, turning first to FIG. 28A, the process flow 2800 begins withthe topic module determining whether input has been received indicatingthe user has selected a selectable part displayed on the window to viewrelated information on the part in Operation 2810. For example, aspreviously discussed, parts (e.g., part names and/or numbers) found inthe textual information on the topic may be displayed as selectable onthe window in various embodiments. If the user has selected a part(e.g., uses a mouse to hover over the part, click on the part, alt-clickon the part, and/or the like), then the topic module generates andprovides a preview to display information on the part to the user inOperation 2815. Here, the preview may be provided in a similar manner asthe other previews described herein. For example, the preview may beprovided on separate window than the window displaying the topic. Asdiscussed further herein, different functionality may be provided on thepreview in some embodiments. For example, the preview may providefunctionality to allow the user to search for other occurrences of thepart in the technical documentation for the item.

In various embodiments, the topic module also determines whether inputhas been received indicating the user has selected a selectableapplicability displayed on the window to view information on theapplicability in Operation 2820. As previously noted, applicabilitygenerally pertains to the context for which the information provided fora topic is valid. Therefore, if the user selects an applicability foundin the content displayed for the topic (e.g., hovers over theapplicability, click on the applicability, alt-clicks on theapplicability, and/or the like), the topic module generates and providesa preview for display providing information on the meaning of theapplicability in Operation 2825. Again, the preview may be provided in asimilar manner as the other previews described herein. For example, thepreview may be provided on separate window than the window displayingthe topic.

In various embodiments, the topic module also determines whether inputhas been received indicating the user would like to view the source datafor the topic in Operation 2830. Here, the source data may represent thesource of the content found in the technical documentation for thetopic. For example, the source data may involve data from a file such asa PDF and/or a SGML file. Therefore, if the user has indicated he or shewould like to view the source data for the topic, then the topic moduleprovides the source data for display in Operation 2835. Here, inparticular embodiments, the source data may be displayed on a separatewindow than the window displaying the topic.

As discussed in further detail herein, this particular functionality maybe configured to perform differently based at least in part on theuser's selection of this functionality. Specifically, in particularembodiments, the user is provided with the corresponding section of thesource data as that currently displayed on the window for the topic inresponse to the user exercising a first type of selection (e.g., singleclick). While the user is provided with the entire source data for thetopic in response to the user exercising a second, different type ofselection (e.g., alt click.

In various embodiments, the topic module also determines whether inputhas been received indicating the user has selected an option to generatean annotation for the topic; in Operation 2840. In various embodiments,annotations may be generated for different content for the topic. Forinstance, the user may generate an annotation with respect to certaintext found in the textual information for a topic and/or the user maygenerate an annotation with respect to other content for the topic suchas an illustration. (e.g., 21) and/or 3D graphic). If the user hasselected the option to generate an annotation for the topic, then thetopic module does so in Operation 2845. In particular embodiments, theannotation can be recorded and stored within the IETM and can only beviewed by the user. While in other instances, others may be able to viewand comment on the annotation.

In particular embodiments, the topic module may provide furtherfunctionality based at least in part on the content of the topicinvolving sequential information. For instance, the topic may involve aprocess, procedure, tasks, checklist, and/or the like that involvesvarious operations and/or steps to be performed. For example, the usermay be viewing a maintenance task involving steps the user is to performfor the task. Therefore, in these particular embodiments, the topicmodule may determine whether the data for the topic (e.g., the datamodule for the topic) involves sequential information in Operation 2850.In some embodiments, the topic module may make such a determinationbased at least in part on the type of content found in the data for thetopic as indicated in the data's metadata (e.g., in the data module'sinformation code). If the content does involve sequential information,then the topic module provides further functionality for the content inOperation 2855.

The additional functionality is now, discussed with respect to FIG. 28B.Therefore, turning now to FIG. 28B, the topic module determines whetherinput has been received indicating the user has acknowledged a step(operation) in a sequence such as a checklist sequence in Operation2860. Typically, the steps found in sequential information (e.g., thesteps found in a checklist) are designed to be performed in thesequential order as listed. Therefore, in particular embodiments, anysteps that are skipped over in the sequence and not acknowledged arehighlighted to bring them to the user's attention. Therefore, as resultof the user acknowledging a step, the topic module checks the stepsequence in Operation 2865.

In addition, in various embodiments, the topic module determines Whetherinput has been received indicating the user has acknowledged an alert inOperation 2870. As previously discussed, in certain embodiments, contentis locked based at least in part on alerts provided in the content. Forexample, the content may provide warnings and/or cautions for the user.Therefore, if the user has acknowledged an alert, the topic moduleunlocks the corresponding content for the alert in Operation 2875.

As discussed further herein, the user may be provided functionality(e.g. an option) in particular embodiments to transfer a job (e.g.,process, procedure, task, checklist, and/or the like) he or she iscurrently performing to another user. For example, the user's work shiftmay be ending and therefore, he or she may wish to transfer the currentjob he or she is performing to another user who is working the followingshift. Therefore, in these embodiments, the topic module may determinewhether input has been received indicating the user has selected theoption to transfer a job in Operation 2880. If so, then the topic modulemay enable functionality to allow the user to transfer the job inOperation 2885.

Further, in various embodiments, functionality may be implemented thatupdates media content provided on the window as the user scrolls throughsequential information. For example, the user may be viewing the stepsfor a maintenance task displayed on a first view pane shown on thewindow. At the same time, illustrations for the maintenance may bedisplayed on a second view pane shown on the window. For instance, astep in the maintenance task may involve a particular component and anillustration of the component may be provided to aid the user inlocating the component on the actual item. Therefore, as the userscrolls through the various steps of the maintenance task, theillustrations provided on the second view pane may change automaticallyin particular embodiments as the user moves from step-to-step anddifferent illustrations are referenced in the steps.

Accordingly, if this is the case, then the topic module determineswhether input has been received indicating the user is scrolling throughthe sequential information in Operation 2886. If the user is scrollingthrough the sequential information, then the topic module updates themedia content displayed on the window accordingly in Operation 2887.

Finally, components are often mentioned in the sequence information. Forexample, the instructions for performing a maintenance task mayreference a particular part that is to be replaced during the task. Manytimes, some type of media may also be provided such as an illustrationto assist the user in actually replacing the part. For instance, theinstructions may be displayed on a first view pane and the illustrationmay be displayed on a second view pane. Here, in particular embodiments,the part may be provided in the first and/or second view panes asselectable. As a result, the user's selection of the part in either thefirst or the second view pane may cause the part to be highlighted inthe other view pane. For example, if the user selects the part in thesequential information, then the part is automatically highlighted inthe illustration to assist the user in locating the part in theillustration. Likewise, if the user selects the part in theillustration, then the part is automatically highlighted in thesequential information to assist the user in determining whichinstructions in the maintenance task the part is involved.

Therefore, if such functionality is provided, then the topic moduledetermines whether input has been received indicating the user hasselected a component in Operation 2888. If the user has selected acomponent, then the topic module highlights the component on the windowaccordingly in Operation 2889.

Returning to FIG. 28A, in particular embodiments, the topic module maybe configured to provide the user with certain functionality at the endof a topic (e.g., at the end of a data module). In some embodiments,some type of selection mechanism (e.g., button) may be provided for thetopic on the window to invoke the functionality when the end of thecontent for the topic has been detected. For example, when the topicmodule detects the user has scrolled to the end of the textualinformation provided for a topic. If such functionality is beingprovided, then the topic module determines whether input has beenreceived indicating the end of the topic has been reached in Operation2890. If so, then the topic module enables the end of topicfunctionality in Operation 2891.

As previously noted, various types of content may be provided indifferent topics. For example, different content types may involveprocedural, fault, parts, process, learning, maintenance, wiring,crew/operator, and/or the like. Thus, in addition to sequentialinformation, various embodiments may provide certain functionality basedat least in part on the topic involving a particular type of content.Therefore, in particular embodiments, the topic module may determinewhether the content for the topic currently being displayed involveswiring data in Operation 2892. If so, then the topic module enableswiring functionality in Operation 2893. Likewise, in particularembodiments, the topic module may determine whether the content for thetopic involves media providing a chart in Operation 2894. If so, thenthe topic module enables crosshairs functionality in Operation 2895.Finally, in particular embodiments, the topic module may determinewhether the content for the topic involves 3D graphics in Operation2896. If so, then the topic module enables 3D graphic functionality inOperation 2897.

At this point, the topic module determines whether input has beenreceived indicating the user wishes to exist viewing the content for thetopic in Operation 2898. For example, the user may have simply selecteda mechanism (e.g., a button) to exit the topic. If that is the case,then the topic module exits. Otherwise, the topic module continues tomonitor the user's interactions.

Similar to the display topic module, the topic module in variousembodiments may invoke various modules to perform some of the operationsjust described. Accordingly, a discussion of these various modules isnow provided.

Display Content for Part Module

Turning now to FIG. 29 , additional details are provided regarding aprocess flow for displaying content for a part according to variousembodiments. FIG. 29 is a flow diagram showing a display content forpart module for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the displaycontent for part module may be invoked by another module to display thecontent such as, for example, the topic module previously described.However, with that said, the display content for part module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

The process flow 2900 begins with the display content for part moduleretrieving the content for the part select by the user in Operation2910. As previously discussed, parts (e.g., part names and/or numbers)found within the textual information of the topic (or other areas of thetechnical documentation) may be displayed as selectable in someembodiments. Therefore, the user may select one of the parts in thetextual information (e.g., use a mouse to hover over the part, click onthe part, alt-clicks on the part, and/or the like). As a result, thedisplay content for part module retrieves related information for thepart to display. For example, the display content for part module mayretrieve metadata from the data (e.g., the data module) found in thetechnical documentation for the part, as well as the topics found in thetable of content in which the part is mentioned.

Once retrieved, the display content for part module provides the contentfor display in Operation 2915. For example, the content may be displayedas a preview as previously discussed. Accordingly, the preview may bedisplayed on a separate window that is superimposed over a portion ofthe window displaying the topic. Here, the displayed content may provideinformation on the part such as, for example, the part name and number.In addition, the content may provide various functionality the user mayinvoke with respect to the part. For example, a selection mechanism(e.g., a hyperlink and/or button) may be provided to allow the user tosearch the technical documentation for the item to identify otherinstances where the part is mentioned/used (e.g., maintenance tasks). Aselection mechanism may also be provided that enables the user to orderthe part from the IETM.

Therefore, in particular embodiments, the display content for partmodule determines whether input has been received indicating the userhas selected the functionality to order the part in Operation 2920. Ifso, then the display content for part module generates and provides theorder form for ordering the part in Operation 2925. For example, thedisplay content for part module invokes the order part module previouslydiscussed (FIG. 19 ) in some embodiments.

In addition, in particular embodiments, the display content for partmodule determines whether input has been received indicating the userhas selected the functionality to search the technical documentation toidentify other instances of the part in Operation 2930. If so, then thedisplay content for part module queries the technical documentation forthe item in Operation 2935. Here, the display content for part modulemay query various items found in the technical documentation such as thetable of contents, data modules, media objects, and/or the like toidentify instances in which the part name and/or number is found. Thedisplay content for part module then provides the results of the searchfor display in Operation 2940.

For example, the display content for part module may be configured insome embodiments to specifically query and identify the maintenanceprocedures/tasks found in the technical documentation in which the partis used and/or involved. Therefore, in these embodiments, the displaycontent for part module provides a list of the maintenanceprocedures/tasks for display for the user to view. The display contentfor part module may be configured to display a set number of theprocedures/tasks such as, for example, five of the procedures/tasks. Thedisplay content for part module may use a number of criteria to identifywhich of procedures/tasks to display such as, for example,alphabetically, more frequently viewed, and/or the like. In addition, aselection mechanism (e.g., a button) may be provided to allow the userto view additional maintenance procedures/tasks for the part.

Further, the display content for part module may provide the list sothat each of the maintenance procedures/tasks displayed is selectable(e.g., displayed as a hyperlink and/or displayed with a selectionmechanism such as a button) so that the user may view a particularmaintenance procedure/task if desired. Therefore, in these particularembodiments, the display content for part module determines whetherinput has been received indicating the user has selected a particularmaintenance procedure/tasks to view in Operation 2945. If so, then thedisplay content for part module retrieves the maintenanceprocedure/tasks and provides the procedure/task for display to the userin Operation 2950.

At this point, the display content for part module determines whetherinput has been received indicating the user would like to exit thedisplay of the content in Operation 2955. If so, then then the displaycontent for part module causes the display of the content be closed andexists. Otherwise, the display content for part module continues monitorthe user's interactions.

FIG. 30 provides an example of a window 3000 providing content for apart 3010 selected by a user according to various embodiments. As onecan see, the window 3000 displaying the content has been superimposedover a portion of the window for the topic in this example. In thisexample, the display of the content provides the user with a selectionmechanism (e.g., a button) 3015 to enable the user to order the partfrom the IETM. In addition, the display of the content lists relatedmaintenance procedures/tasks 3020 in which the part is used and/ormentioned. Further, the display of the content provides a selectionmechanism (e.g., a button) 3025 to view additional maintenanceprocedures/tasks in which the part is used and/or mentioned.

Display Content for Applicability Module

Turning now to FIG. 31 , additional details are provided regarding aprocess flow for displaying content for applicability according tovarious embodiments. FIG. 31 is a flow diagram showing a display contentfor applicability module for performing such functionality according tovarious embodiments of the disclosure. In particular embodiments, thedisplay content for applicability module may be invoked by anothermodule to display the content such as, for example, the topic modulepreviously described. However, with that said, the display content forapplicability module may not necessarily be invoked by another moduleand may execute as a stand-alone module in other embodiments.

The process flow 3100 begins with the display content for applicabilitymodule retrieving the content for the applicability select by the userin Operation 3110. As previously discussed, applicability found withinthe textual information of the topic (or other areas of the technicaldocumentation) may be displayed as selectable in some embodiments.Therefore, the user may select one of the occurrences of applicabilityin the textual information (e.g., use his or her mouse to hover over theoccurrence, click on the occurrence, alt-click on the occurrence, and/orthe like) As a result, the display content for applicability moduleretrieves related information for the applicability to display. Forexample, the display content for applicability module may retrieveinformation on the meaning of the applicability as it pertains to theitem.

Once retrieved, the display content for applicability module providesthe content for display for the user to view in Operation 3115. Forexample, the content may be displayed as a preview as previouslydiscussed. Accordingly, the preview of the content may be displayed on aseparate window that is superimposed over a portion of the window forthe topic.

FIG. 32 provides an example of a window 3200 displaying content providedfor an occurrence of applicability 3210 selected by a user according tovarious embodiments. As one can see, the window 3200 display the contenthas been superimposed over a portion of the window for the topic in thisexample. Here, the content provides the user with a rule 3215 for a listof components (e.g., engines) in which the applicability applies.

Display Source for Topic Module

Turning now to FIG. 33 , additional details are provided regarding aprocess flow for displaying the source for a topic according to variousembodiments. FIG. 33 is a flow diagram showing a display source fortopic module for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the displaysource for topic module may be invoked by another module to display thesource such as, for example, the topic module previously described.However, with that said, the display source for topic module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

As previously mentioned, the user may indicate he or she would like toview the source data for a topic. The source data may represent thesource of the content found in the technical documentation for thetopic. For example, the source data may involve data from a file such asa PDF and/or a SGML file. Therefore, if the user has indicated he or shewould like to view the source data for the topic, then the process flow3300 begins with the display source for topic module determining whetherinput has been received indicating the user would like to view a sectionfrom the source or the entire source in Operation 3310.

Also previously discussed, the user may be provided with multipleactions to select the selection mechanism in particular embodiments toindicate what from the source he or she would like to view.Specifically, in particular embodiments, the user is provided with thecorresponding section of the source data as that is currently displayedon the window for the topic in response to the user exercising a firsttype of selection (e.g., single click). While the user is provided withthe entire source data for the topic in response to the user exercisinga second, different type of selection (e.g., alt-click).

Therefore, if the display source for topic module determines the userhas exercised the first type of selection, then the display source fortopic module retrieves the corresponding section (e.g., pages) of thesource in Operation 3315 and provides the section of the source fordisplay in Operation 3320. For example, the section of the source may bedisplayed on a window that is superimposed over a portion of the windowdisplay the topic in some embodiments. While in other embodiments, thesection of the source may be displayed on a separate view pane on thewindow.

However, if the display source for topic module determines the user hasexercised the second type of selection, then the display source fortopic module retrieves the entire source in Operation 3325 and providesthe entire source for display in Operation 3330. Again, the entiresource may be displayed on a window that is superimposed over a portionof the window display the topic in some embodiments. While in otherembodiments, the entire source may be displayed on a separate view paneon the window.

FIG. 34A provides an example of displaying a section of a source for atopic according to various embodiments. Here, a selection mechanism 3400is displayed on a window that is configured so that the user is providedwith multiple actions to select the mechanism 3400. Accordingly, if theuser exercises a first type of selection (e.g., click) of the mechanism3400, then a separate window 3410 is displayed that provides a sectionfrom the source (in this example, a pdf) as shown as in this example aspage five of the source 3415. However, if the user exercises a second,different type of selection (e.g., alt-click) of the mechanism 3400,then a separate window is displayed that provides the entire source asshown as all five pages 3420 in FIG. 34B.

Generate Annotation Module

Turning now to FIG. 35 , additional details are provided regarding aprocess flow for generating an annotation according to variousembodiments. FIG. 35 is a flow diagram showing a generate annotationmodule for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the generateannotation module may be invoked by another module to generate anannotation such as, for example, the topic module previously described.However, with that said, the generate annotation module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

As previously noted, a user may add an annotation to various contentdisplayed for a topic such as in the textual information and/or mediacontent such as an illustration. Therefore, the process flow 3500 beginswith the generate annotation module receiving where (e.g., receivinginput identifying where) in the content for the topic the annotation isto be placed in Operation 3510. Note that in particular embodiments, anannotation may not necessarily be placed in the content of a topic butmay be place at other locations in the technical documentation of anitem such as, for example, in the table of contents.

The generate annotation module then provides the annotation in Operation3515. Specifically, in particular embodiments, the generate annotationmodule may generate and provide the annotation to display on a separatewindow than the window displaying the topic. Accordingly, the window maydisplay initial information for the annotation such as, for example, thedate and time the annotation was generated. In addition, the user may beprovided with different types of annotations that may be added to thecontent such as a personal note, a question, a warning and/or missinginformation, a problem, and/or the like. Therefore, the initialinformation may also indicate the type of annotation.

Depending on the embodiment, the generate annotation module may providevarious functionality with respect to the annotation. Therefore, inparticular embodiments, the generate annotation module determineswhether input has been received indicating the user would like to add anattachment to the annotation in Operation 3520. For example, the usermay wish to attach a text document, image, and/or screenshot of thewindow (e.g., image of the window) and the user selects a selectionmechanism (e.g., a button) provided on the window for the annotation. Inresponse, the generate annotation module provides a capability for theuser to identify the file to attach to the annotation. For example, thegenerate annotation module may cause display of a window that allows theuser to navigate to a location where the file is locate and attach thefile to the annotation. Accordingly, the generate annotation module isconfigured in various embodiments to enable the attachment of a file ina variety of formats such as JPEG, JPEG2000, EXIF, TIFF, RAW, DIV, GIF,BMP, PNG, PPM, MOV, AVI, MP4, MKV, DOCX, HTMLS, TXT, PDF, XML SGML, JSONand/or the like. Therefore, if the user has indicated he or she wouldlike to attach a file to the annotation, then the generate annotationmodule attaches the file in Operation 3525.

In addition, the generate annotation module may determine whether inputhas been received indicating the user would like to share the annotationwith other users in Operation 3530. In some embodiments, an annotationmay normally only be available to view to the user who generated theannotation. However, there may be instances in which the user may wantto share his or her annotation with other users and ask for comments.For example, the user may identify an error he or she believes is in thetechnical documentation for a topic. Therefore, the user may decide toplace an annotation in the topic on the error and ask other userswhether they also agree on the error in the documentation. Accordingly,such functionality can allow for crowd sourcing to address issues in thetechnical documentation and/or to assist a user in using thedocumentation. Therefore, if the user has indicated he or she would liketo share the annotation, then the generate annotation module sets theannotation to share in Operation 3535.

Further, the generate annotation module may determine whether input hasbeen received indicating the user may want to submit a change requestbased at least in part on the annotation in Operation 3540. Inparticular embodiments, a formal procedure may be put in place to allowusers of the IETM to submit change requests to have content changed inthe technical documentation for an item. For example, a user may beviewing the textual information on a topic and may decide to generate anannotation for a section of the textual information the user does notbelieve is quite clear and should be further explained in theinformation. Therefore, the user may wish to submit a change requestbased at least in part on his or her annotation. If that is the case,then the generate annotation module may provide a change request form todisplay for the user in Operation 3545.

In some embodiments, the generate annotation module may auto-populatesome of the fields provided on the form based at least in part on theinformation found in the annotation in Operation 3550. For example, thegenerate annotation module may auto-populate the fields in which theuser provides his or her name, a date, an identifier for the topic(e.g., a DMC), and/or any comments for the request that have beenprovided in the annotation. The user may then fill any additionalinformation needed on the form and select a mechanism provided on theform to submit the request for change.

Therefore, the generate annotation module determines whether input hasbeen received indicating the user has submitted the change request formin Operation 3555. If the user has submitted the form, then the generateannotation module submits the change request form in Operation 3560. Asa result, the change request form may be sent to personnel who areresponsible for maintaining the technical information for the item.Accordingly, such personnel may include those individuals who areresponsible for maintaining the IETM and/or the publication of thetechnical documentation currently uploaded to the IETM for the itemand/or those individuals who are responsible for maintaining the sourcetechnical documentation used in producing the publication that has beenuploaded into the IETM.

Finally, the generate annotation module may determine whether input hasbeen received indicating the user would like to capture a screenshot(e.g., an image) of the window and the content currently being displayedon the window in Operation 3565. In many instances, the user may wish toattach a screenshot of the window to the annotation to provide moreexplanation for the annotation. Therefore, if the user would like tocapture a screenshot of the window, the generate annotation modulegenerates the screenshot in Operation 3570.

At this point, the generate annotation module determines whether inputhas been received indicating the user would like to exit the windowdisplaying the annotation in Operation 3575. It is noted that inparticular embodiments, the annotation is automatically generated andrecorded in the IETM at the time the user selects the option (e.g., theselection mechanism) on the window for the topic. Therefore, in theseparticular embodiments, any additional information provided by the useron the annotation is recorded for the annotation when the user existsthe window displaying the annotation. However, in other embodiments, theuser may be required to take some action such as select a mechanism(e.g., a button) provided on the window displaying the annotation and/orthe topic to record the annotation. Furthermore, different selectionmechanisms (e.g., buttons) may be provided on the window displaying theannotation and/or on the topic to invoke the functionality describedabove.

Finally, the various functionality provided by the generate annotationmodule described above may also be made available to users once theannotations have been recorded in the IETM. For example, a user may beable to sign into the IETM and view an annotation he or she hadpreviously added to the technical documentation of an item. At thistime, in particular embodiments, the functionality such as attaching afile and/or submitting a change request may be made available to theuser.

FIG. 36A provides an example of an annotation window 3600 displayedaccording to various embodiments. In this example, the user hasidentified an area 3610 in an illustration displayed for a topic andadded a note of “bad region.” The annotation window 3600 provides afirst selection mechanism 3615 to allow the user to attach a file 3620to the annotation such as a screenshot of the window displaying thetopic. Accordingly, the annotation window 3600 provides a secondselection mechanism 3625 that enables the user to take the screenshot ofthe window displaying the topic. In addition, the annotation window 3600in the example provides a third selection mechanism 3630 that allows theuser to share the annotation with other users. Finally, the annotationwindow 3600 provides a fourth selection mechanism 3635 that facilitatesthe user submitting a change request based at least in part on theannotation. Accordingly, a change request form 3640 that may be providedin some embodiments in shown in FIG. 36B.

FIG. 36C provides an example of a selection mechanism 3645 that may beprovided in particular embodiments to enable a user to generate anannotation. Here, the selection mechanism 3645 is a dropdown menucontrol provided in a toolbar displayed along the top of a window thatprovides the user with options for generating different types ofannotations. In particular embodiments, the IETM may provide the userwith a report 3650 on the change requests that have been submitted bythe user as shown in FIG. 36D. Finally, in particular embodiments, theIETM may provide the user with a list of all the annotations 3655 thathave been generated by the user as shown in FIG. 36E. In someembodiments, this list 3655 may also display annotations that have beenshared by other users.

Sequence Skip Module

Turning now to FIG. 37 , additional details are provided regarding aprocess flow for checking the steps (operations) found in a sequenceaccording to various embodiments. FIG. 37 is a flow diagram showing asequence skip module for performing such functionality according tovarious embodiments of the disclosure. In particular embodiments, thesequence skip module may be invoked by another module to check the stepspreformed in a sequence such as, for example, the topic modulepreviously described. However, with that said, the sequence skip modulemay not necessarily be invoked by another module and may execute as astand-alone module in other embodiments.

As previously noted, additional functionality may be provided in variousembodiments for content involving sequential information. One suchfunctionality involves highlighting any steps skipped in a sequence suchas a checklist upon the user acknowledging performing a step in thesequence. Typically, the steps found in sequential information (e.g.,the steps found in a checklist) are designed to be performed in thesequential order in which they are listed. Therefore, in particularembodiments, any steps that are skipped over in the sequence and notacknowledged are highlighted to bring them to the user's attention.

Therefore, the process flow 3700 begins with the sequence skip moduledetermining whether a step acknowledged by the user is the next step inthe sequence to be performed by the user in Operation 3710. For example,in particular embodiments, the user may be provided a field (e.g., acheckbox) in the sequential information that the user is able to checkas he or she completes steps in the sequence. Therefore, in theseembodiments, the sequence skip module receives input on the fields anddetermines Which of the fields have been checked by the user.Accordingly, if the sequence skip module determines the stepacknowledged by the user is not the next sequential step to beperformed, then the sequence skip module causes the steps in thesequence that have been skipped by the user to be displayed ashighlighted in the sequential information displayed on the window inOperation 3715.

An example of a window displaying sequence information in which stepshave been skipped 3800 are highlighted in accordance with variousembodiments is shown in FIG. 38 . In this example, the user hasacknowledged a step 3810 that is not the next step to perform in thesequence based at least in part on the steps already acknowledged by theuser. Therefore, as a result, the prior steps 3800 that have not beenacknowledged by the user are highlighted to bring them to the user'sattention.

Unlock Content Module

Turning now to FIG. 39 , additional details are provided regarding aprocess flow for unlocking content as a result of a user acknowledgingan alert according to various embodiments. FIG. 39 is a flow diagramshowing an unlock content module for performing such functionalityaccording to various embodiments of the disclosure. In particularembodiments, the unlock content module may be invoked by another moduleto unlock content such as, for example, the topic module previouslydescribed. However, with that said, the unlock content module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

In various embodiments, a portion of the content provided for a topicmay be locked to require a user to acknowledge an alert associated withthe portion of the content. For example, the content may provide awaning and/or caution for the user. Accordingly, the user may,acknowledge the alert. For example, some type of mechanism such as abutton may be provided that the user selects to acknowledge the alertand as a result, the unlock content module is invoked.

Therefore, the process flow 3900 begins with the unlock content moduleidentifying the alert that has been acknowledged in Operation 3910.Here, in particular embodiments, the unlock content module may receiveand/or read a tag associated with the alert that is provided in thetextual information for a topic. Accordingly, the tag identifies thealert and its location with respect to the other content found in thetextual information.

Next, the unlock content module identifies the next alert in the contentin Operation 3915. Again, in particular embodiments, the unlock contentmodule may identify the next tag found in the textual information for analert. In some instances, the alert acknowledged by the user may be thelast alert provided in the content. If that is the case, then the unlockcontent module may identify the end of the content.

Finally, the unlock content module unlocks the portion of the contentbetween the two alerts in Operation 3920. As previously discussed, thecontent may be locked using a number of different approaches and/or anycombination thereof. For instance, the user's ability to view theportion of the content may be obscured. For example, the portion of thecontent may be greyed out so that it cannot be read. In addition, anyinteractive functionality found within the portion of the content may bedisabled. For example, the portion of the content may contain anoccurrence of a selectable part. Here, the selectable functionality ofthe part may be disabled. In some instances, the user's ability toscroll through the portion of the content may be disabled. However theportion of the content has been locked, the unlock content moduleperforms the necessary operations to unlock the content.

It is noted that in various embodiments not all of the content that hasbeen locked is unlock as a result of the user acknowledging the alert.Generally speaking, only the portion of the content that is availablebetween the acknowledged alert and the next alert found in the contentis unlock. Such a configuration can be used to ensure that the userviews and acknowledges each and every alert provided in the content asthe user moves through the content. However, with that said, otherconfigurations may be used in unlocking the content based at least inpart on the user acknowledging alerts. For example, some embodiments mayrequire the user to acknowledge multiple alerts before unlockingcontent. Those of ordinary skill in the art can envision otherconfigurations that may be used in other embodiments in light of thisdisclosure.

FIG. 40A provides an example of a portion of content 4000 that has beenlocked according to various embodiments. Specifically, the portion ofthe content 4000 has been greyed out to obscure the user's ability toview the portion of the content 4000. An alert is displayed thatprovides an acknowledgment mechanism (e.g., a button) 4010 that can beselected by the user to acknowledge the alert and unlock the portion ofthe content 4000. As a result of the user acknowledging the alert, thatis as a result of the user selecting the acknowledgment mechanism 4010,the portion of the content 4015 is unlock as shown in FIG. 40B. Here,the portion of the content 4015 is unlock to the next alert found in thecontent. At this point, the user can select the acknowledgment mechanism4020 for the next alert to unlock additional content.

Transfer Job Module

Turning now to FIG. 41 , additional details are provided regarding aprocess flow for facilitating a user transferring a job according tovarious embodiments. FIG. 41 is a flow diagram showing a transfer jobmodule for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the transferjob module may be invoked by another module to transfer a job such as,for example, the topic module previously described. However, with thatsaid, the transfer job module may not necessarily be invoked by anothermodule and may execute as a stand-alone module in other embodiments.

As previously discussed, a user may wish to transfer a job (e.g., aparticular instance of a process, procedure, task, checklist, and/or thelike) he or she is currently performing to another user. For example,the user's work shift may be ending and therefore, he or she may wish totransfer the current job he or she is performing to another user who isworking the following shift. Therefore, in these embodiments, the usermay select an option (e.g., a button) to transfer a job and as a result,the transfer job module is invoked.

The process flow 4100 begins with the transfer job module causingdisplay of an indication (e.g., a divider) at a point in the contentbeing displayed on a window where the user is suspending performing thejob in Operation 4110. For instance, if the user is performing a jobinvolving a maintenance procedure/task that includes several steps, thenthe transfer job module causes the indicator to be displayed between thetwo steps of the procedure/task where the user is stopping. Accordingly,depending on the embodiment, the indication may be displayed in a numberof different formats such as a line, arrow, bullet point, and/or thelike.

The transfer job module then generates a job transfer window based atleast in part on the job in Operation 4115 and provides the window fordisplay in Operation 4120. Here, the transfer job window may besuperimposed over a portion of the window displaying the procedure/task.The job transfer window may provide information such as the title of theprocedure/task being performed for the job (e.g., the DMC for therelated data module), the user's name, a data and time the job issuspended, a job control number, comments provided by the user, and/orthe like. The transfer job module then records the job transfer in theIETM in Operation 4125. This operation in particular embodimentsinvolves the transfer job module recording a marker identifying wherethe job was suspended. Accordingly, this marker can then be used at alater time in identifying where the job needs to be resumed.

As a result, the job transfer may now be posted in the IETM so thatanother user may resume the job. Depending on the embodiment, the jobtransfer may be viewed by every user who signs into the IETM for theitem and/or specific object for the item or the job transfer may only beviewed by those users who can resume the job. That is to say, inparticular embodiments, the job transfers available to a user to viewand/or resume may be dependent on the credentials used by the user insigning into the IETM.

Resume Job Module

Turning now to FIG. 42 , additional details are provided regarding aprocess flow for resuming a suspended job according to variousembodiments. FIG. 42 is a flow diagram showing a resume job module forperforming such functionality according to various embodiments of thedisclosure. In particular embodiments, the resume job module may beinvoked as a result of a user signing into the IETM and selecting anoption to view the jobs that have been suspended.

The process flow 4200 begins with the resume job module receiving inputindicating a selection from a user to view the jobs that have beensuspended in Operation 4210. For instance, in particular embodiments,the user may be provided with a mechanism such as a button on a toolbarto view the jobs that have been suspended. In response to the userselecting the mechanism, the resume job module may provide the suspendedjobs to display on a window to the user in Operation 4215. Here, thewindow may be configured to allow the user to select a particular jobfrom the suspended jobs.

Therefore, the resume job module determines whether input has beenreceived indicating the user has selected a job displayed on the windowto resume in Operation 4220. If so, then the resume job module retrievesthe stop position for the job in Operation 4225. As previously noted, amarker may be recorded when the job was transferred that identifies theposition where the job was suspended. Once the marker has beenretrieved, the resume job module provides the procedure/tasks associatedwith the suspended job for display on a window to the user along with anindication (e.g., a divider) based at least in part on the marker inOperation 4230. In addition, the resume job module provides a resume jobwindow for display in Operation 4235. Here, the resume job window may besuperimposed over a portion of the window displaying the procedure/taskand may provide a mechanism (e.g., a button) that the user can select toresume the job.

Thus, the resume job module determines whether input has been receivedindicating the user will resume the j ob in Operation 4240. If the userhas decided to resume the job, then the resume job module causes theresume job window to close and causes the indication to be removed inOperation 4245. Accordingly, the job that has been resumed may beremoved from the suspended jobs. Otherwise, the resume job moduledetermines whether input has been received indicating the user wouldlike to exit viewing the suspended jobs in Operation 4250. If the userdoes want to exit, then the resume job module causes the display of thesuspended jobs to be closes and exits.

FIG. 43A provides an example of a mechanism 4300 that is provided inparticular embodiments to enable a user to transfer or resume a job. Inthis example, the mechanism 4300 is a dropdown menu control provided ina toolbar displayed along the top of a window. Here, the dropdown menuprovides the user with the option to create a job transfer 4310 and theoption to open the jobs that have been transferred (suspended) 4315.FIG. 43B provides an example of a job transfer window 4320 according tovarious embodiments. As noted above, such a window 4320 may be providedin particular embodiments when a user selects an option to transfer ajob the user is currently performing. FIG. 43C provides an example of aprocedure/task that has been suspended that a user has identified toresume. Accordingly, an indication 4325 is shown in the display of theprocedure/task at a position where the procedure/task was suspended. Inaddition, a resume job window is provided along with a mechanism (e.g.,a button) 4330 to allow the user to resume the job. Finally, FIG. 43Ddisplays the procedure/task for the job with the indication 4335removed. At this point, the user can resume the job and finish theremaining steps for the procedure/task.

Update Media Module

Turning now to FIG. 44 , additional details are provided regarding aprocess flow for updating the media content displayed based at least inpart on a user scrolling through textual information according tovarious embodiments. FIG. 44 is a flow diagram showing an update mediamodule for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the updatemedia module may be invoked by another module to update the mediacontent displayed such as, for example, the topic module previouslydescribed. However, with that said, the update media module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

For example; a user may be viewing the steps for a maintenance taskdisplayed on a first view pane on a window. At the same time,illustrations for the maintenance may be provided on a second view pane.For instance, a step in the maintenance task may involve a particularcomponent and an illustration of the component may be provided to aidthe user in locating the component on the actual item. Accordingly, inparticular embodiments, the window may be configured to display the twopanes on non-overlapping portions of the window.

Therefore, as the user scrolls through the various steps of themaintenance task, the process flow 4400 begins with the update mediamodule identifying the first occurrence of media content mentioned inthe textual information displayed on the window in Operation 4410. Invarious embodiments, the first occurrence is determined from the top ofthe window. Therefore, the update media module searches the textualinformation starting at the top of the window until the module finds areference to media content in the text. For example; the first referenceto media content may be a reference to a figure, a video, an image, asound recording, and/or the like.

The update media module then retrieves the media content associated withthe reference in Operation 4415. In particular embodiments, thereference to the media may include a hyperlink that the user may selectto retrieve the media content if desired. Therefore, the update mediamodule may obtain the storage location of the media content in the IETMfrom the hyperlink and retrieve the media content from the storagelocation. In other embodiments, the update media module may obtain thestorage location from the data (e.g., data module) for the textualinformation being viewed. In other embodiments, the update media modulemay use other processes for retrieving the media content as those ofordinary skill in the art can envision in light of this disclosure. Onceretrieved, the update media module updates the view pane used fordisplaying media by causing the retrieved media content to be displayedin the view pane in Operation 4420.

FIG. 45 provides an example of media content being updated as a userscrolls through the textual information for a topic according to variousembodiments. As shown in this example, the first occurrence of mediacontent mentioned in the textual information shown in the view panedisplayed on the left side of a window is FIG. 2 , Sheet 2 4500. As aresult, the corresponding illustration for FIG. 2 , Sheet 2 4510 isshown in the view pane displayed on the right side of the window. Oncethe user has scroll down the textual information so that the referenceto FIG. 2 , Sheet 2 can no longer be seen in the view pane, then themedia content displayed in the view pane on the right is updated toreflect the media content that is now the first to be referenced in thetextual information. It is noted that in particular embodiments multipleview panes may be used to display the media content so that multipleoccurrences of media content mentioned in the textual information may beshown on a window at the same time.

Highlight Unit Module

Turning now to FIG. 46 , additional details are provided regarding aprocess flow for highlighting a unit displayed in media content such asan illustration (e.g., 2D or 3D graphic) or mentioned in text based atleast in part on a user selecting the unit according to variousembodiments. FIG. 46 is a flow diagram showing a highlight unit modulefor performing such functionality according to various embodiments ofthe disclosure. In particular embodiments, the highlight unit module maybe invoked by another module to highlight a unit such as, for example,the topic module previously described. However, with that said, thehighlight unit module may not necessarily be invoked by another moduleand may execute as a stand-alone module in other embodiments.

The term. “unit” may refer to a component of an item, equipment, a tool,and/or the like. Accordingly, a unit may be referenced in the textualinformation for a topic, as well as displayed in media content such asan illustration. For example, a user may be being viewing theinstructions for performing a maintenance task and the instructions mayreference a particular part that is to be replaced during the task. Manytimes, some type of media may also be provided such as an illustrationto assist the user in actually replacing the part. For instance, theinstructions may be displayed on a first view pane of a window and theillustration may be displayed on a second view pane of a window. Here,in particular embodiments, the part may be provided in the first and/orsecond view panes as selectable. Although the part may not necessarilybe selectable. Therefore, in response to the user selecting one or moreunits in one of the view panes, the highlight unit module may beinvoked.

The process flow 4600 begins with the highlight unit module determiningwhether input has been received indication a selection of textreferencing one or more units in Operation 4610. For example, the usermay be viewing the steps for a maintenance procedure/task and may selecta particular step for the procedure/task in the textual informationdisplayed on a window. Accordingly, the step may refer to one or moreunits (e.g., one or more components). The highlight unit module may beconfigured to identify the reference(s) to the unit(s) based at least inpart on the unit(s) (e.g., unit name and/or number) being selectablewithin the textual information. In other embodiments, the highlight unitmodule may be configured to identify the reference(s) to the units(s) bysearching the selected text and comparing terms within the text to alist of units(s) (e.g., component names, part names and/or numbers,and/or the like).

The highlight unit module then causes the unit(s) to be displayed ashighlighted in the media content being displayed on the window inOperation 4615. Accordingly, the highlight unit module may highlight theunit(s) using different formatting depending on the embodiment. Forinstance, the highlight unit module may highlight the unit(s) in themedia content by displaying the unit(s) in bold, in a particular color,with a marker, with a border, in a different font, any combinationthereof, and/or the like. As a result, the user is then able to identifythe unit(s) referenced in the selected text in the media content moreeasily.

The highlight unit module is configured in various embodiments toperform similar functionality in respect to the user selecting one ormore units displayed in the media content. Therefore, if the highlightunit module determines it has not received a selection of textcontaining one or more units, then the module determines whether it hasreceived a selection of one or more units in the media content currentlybeing displayed on the window in Operation 4620. The unit(s) displayedin the media content may be selectable and therefore, the user may haveselected one or more of the units displayed in the media content. Forexample, the user may select a unit by clicking on the unit in the mediacontent. In particular instances, the user may be able to selectmultiple units by holding down a key while clicking on the units suchas, for example, the ctrl key or the alt key. Those of ordinary skill inthe art can contemplate other approaches that may be used to select theunit(s) in the media content in light of this disclosure.

Similar to the user selecting text referencing one or more units, thehighlight unit module then causes the unit(s) to be displayed ashighlighted in the textual information being displayed on the window inOperation 4625. Again, the highlight unit module may highlight theunit(s) using different formatting depending on the embodiment.

FIG. 47A provides an example of a window displaying a first view pane onthe right side of the window providing the textual information for atopic and a second view pane on the left side of the window providing anillustration or the topic. In this example, the user has selected aparticular step 4700 of a procedure/task referencing parts 4710, 4715,4720 displayed in the illustration and a result, the parts 4725, 4730,4735 have been automatically highlighted in the illustration accordingto various embodiments. FIG. 47B provides an example in which the userhas selected a part 4740 in the illustration in the view pane displayedon the right side of the window and the references to the part 4745,4750 are automatically highlighted in the textual information in theview pane displayed on the left side of the window according to variousembodiments.

End of Topic Module

Turning now to FIG. 48 , additional details are provided regarding aprocess flow for providing functionality when a user has reached the endof a topic according to various embodiments. FIG. 48 is a flow diagramshowing an end of topic module for performing such functionalityaccording to various embodiments of the disclosure. In particularembodiments, the end of topic module may be invoked by another module toinvoke functionality such as, for example, the topic module previouslydescribed. However, with that said, the end of topic module may notnecessarily be invoked by another module and may execute as astand-alone module in other embodiments.

As previously mentioned, various embodiments provide the user withcertain functionality when the end of the content for a topic has beendetected. For example, the topic module may invoke the end of topicmodule in response to detecting the user has scrolled to the end of thetextual information provided for a topic. As previously noted, thecontent for a topic may be formatted in various embodiments according toS1000D standards. Therefore, the content for a topic may be stored inthe IETM with respect to data modules and the end of the topic may referto the end of content found in a particular data module for the topic(e.g., the end of the data module).

Further, the functionality may only be provided at the end of the topicin particular embodiments to ensure the user has viewed and/orprocessed/used all of the content for a topic. For example, the user maybe viewing a topic involving a task with many steps that are to beperformed by the user. Therefore, end of topic functionality may only beprovided upon detecting the user has reached the end of the content,that is reached the end of the steps for the task, to ensure the userhas performed all of the steps. In some embodiments, other criteria mayalso be associated with providing end of topic functionality. Forinstance, returning to the example, the user may also need toacknowledge he or she has performed all of the steps in the tasks bychecking off the steps before the end of topic functionality isprovided.

Accordingly, the process flow 4800 begins with the end of topic moduleproviding of an end of topic mechanism (e.g., a button) for the contentdisplayed for the topic on a window in Operation 4810. In addition, theend of topic module in particular embodiments provides a previous topicmechanism (e.g., a button) and a next topic mechanism (e.g., a button)for the content displayed for the topic on the window in Operations4815, 4820.

At this point, the end of topic module determines whether input has beenreceived indicating the user has selected the previous topic mechanismin Operation 4825. If so, then the end of topic module generates apreview for the previous topic found just before the current topic beingviewed by the user in the table of contents for the technicaldocumentation in Operation 4830 and provides the preview for display inOperation 4835.

For instance, in particular embodiments, the previous topic preview maybe provided as a separate window than the window displaying the topic.In some embodiments, the preview window may be superimposed over aportion of the window displaying the topic. Accordingly, the previoustopic preview may provide the user with information/data, tables,instructions, illustrations, other media content, links to additionaland/or related information, and/or the like associated with the previoustopic. In some embodiments, the preview is configured to provide only apreview of some of the content found in the technical documentation onthe previous topic. For example, the preview may be configured inparticular embodiments to provide the first five to fifty lines oftextual information that the user would be provided with if the userwere to select the previous topic to view the entire content for thetopic.

If the user has not selected the previous topic mechanism, then the endof topic module determines whether input has been received indicatingthe user has selected the next topic mechanism in Operation 4840. If so,then the end of topic module generates a preview of the next topic foundjust after the current topic being viewed by the user in the table ofcontents for the technical documentation in Operation 4845 and providesthe preview for display in Operation 4850. Accordingly, the preview forthe next topic may be configured in the same manner as the preview forthe previous topic.

However, if the user has not selected the next topic mechanism, then theend of topic module determines whether input has been receivedindicating the user has selected the end of topic mechanism in Operation4855. If so, then the end of topic module executes the functionalityassociated with the end of topic mechanism in Operation 4860. Thefunctionality may perform different operations depending on theembodiment. For instance, in some embodiments, the functionality mayopen the table of contents for the technical documentation at the placein the table of contents where the current topic being viewed by theuser is located and may highlight the current topic in the table ofcontents. Here, the table of contents may be provided in a separatewindow and/or a view pane displayed on the window displaying the topic.Such functionality may allow the user to then view other topics in thevicinity of the current topic to help the user navigate to a new topic.In other embodiments, the functionality may take the user back to thetop of the content for the topic (e.g., back to the top of the datanodule).

In other embodiments, the functionality may allow the user to view otherobjects for the item. For example, the user may be performingmaintenance on a particular aircraft of a type of aircraft found in anairline's fleet and may be viewing a maintenance task. Accordingly, theuser may be signed into the IETM using credentials identifying theparticular aircraft so that the maintenance work (e.g., job) beingperformed on the aircraft is tracked and recorded. However, the user maybe assigned to perform the same maintenance on another aircraft of thesame type found in the airline's fleet. Therefore, the end of the topicfunctionality may allow the user to view the other aircraft of the sametype in the airline's fleet and then enable the user to move easily tothe other aircraft in the IETM (e.g., sign-into the other aircraft inthe IETM) while maintaining the same maintenance task (e.g., the sametopic). Those of ordinary skill in the art can envision otherfunctionality may be invoked in other embodiments in light of thisdisclosure. It is noted that although not shown in the process flow 4800provided in FIG. 48 , the end of topic module is configured in someembodiments to cause the end of topic mechanism, the previous topicmechanism, and/or the next topic mechanism to be removed from display ifthe user scrolls to the position in the content for the topic that is nolonger at the end of the content.

FIG. 49A provides an example of an end of topic mechanism (e.g., abutton) 4900 provided at the end of the content for a topic according tovarious embodiments. FIG. 49B provides an example in which thefunctionality performed as a result of the user selecting the end oftopic mechanism 4900 is displaying a window with the table contents at aposition 4910 in the table of contents highlighting the current topicbeing viewed by the user.

Wiring Module

Turning now to FIG. 50 , additional details are provided regarding aprocess flow for providing functionality for wiring data according tovarious embodiments. FIG. 50 is a flow diagram showing a wiring modulefor performing such functionality according to various embodiments ofthe disclosure. In particular embodiments, the wiring module may beinvoked by another module to invoke functionality such as, for example,the topic module previously described. However, with that said, thewiring module may not necessarily be invoked by another module and mayexecute as a stand-alone module in other embodiments.

As previously noted, various types of content may be provided indifferent, topics. One such type of content is wiring data. Forinstance, content involving wiring data may provide one or moreillustrations of an electrical schematic of a wiring configuration usedfor the item. The electrical schematic may include a layout of aplurality of wires and a plurality of other components that make up theconfiguration. The other components may include articles such asharnesses, electrical equipment, connectors (e.g., plugs), trackassemblies, and/or the like. Therefore, in particular embodiments, thetopic module may determine whether the content for the topic currentlybeing displayed involves wiring data and if so, the topic module invokesthe wiring module.

Therefore, the process flow 5000 begins with the wiring moduledetermining whether input has been received indicating the user who isviewing wiring data has select a particular wire in the electricalschematic being displayed on a window in Operation 5010. As noted, thewiring data may entail one or more illustrations of the electricalschematic. Here, the individual wiring and/or components shown in theillustration(s) may be configured as selectable to invoke differentfunctionality depending on the type of selection mechanism used by theuser.

For instance, in some embodiments, the individual wiring may beconfigured so that if the user uses his or her mouse to hover over aparticular wire shown in the schematic, then tracing of the wire in theschematic is displayed on the window. Here, the tracing may be shown byhighlighting the wire in the schematic by, for example, bolding thewire, displaying, the wire in a particular color, displaying the wireusing a unique pattern, using a combination thereof, and/or the like.

However, if the user selects the particular wire using a second,different selection mechanism (e.g., clicking on the wire), then thewiring module generates a preview for the wire and provides the previewfor display in Operations 5011 and 5012. Similar to other previews, thewire preview may be provided as a separate window than the windowdisplaying wiring data. In some embodiments, the preview window may besuperimposed over a portion of the window displaying the wiring data.Accordingly, the wire preview may provide the user withinformation/data, tables, instructions, illustrations, other mediacontent, links to additional and/or related information, and/or the likeassociated with the wire. In some embodiments, the preview is configuredto provide only a preview of some of the content found in the technicaldocumentation on the wire.

However, if the wiring module instead determines input has been receivedindicating the user has selected the particular wire using a third,different selection mechanism (e.g., alt-clicking on the wire) inOperation 5013, then the wiring module enables live wire for theparticular wire in Operation 5014. As discussed further herein, livewire provides a window displaying a diagram with all of the terminalends for the selected wire. Accordingly, the window is configured inparticular embodiments so that the user can select portions of the wirebetween terminal ends within the diagram to view information on theportion of wire and terminal ends.

If the user has not selected a wire in the electrical schematic, thenthe wiring module determines whether input has been received indicatingthe user has selected a component (other than a wire) displayed in theschematic in Operation 5020. If so, then the wiring module generates apreview for the component and provides the preview for display inOperations 5021 and 5022. Accordingly, the preview for the component maybe configured in the same manner as the preview for the wire.

For example, the component selected by the user may be a connectordisplayed in the electrical schematic of the wiring configuration usedfor the item. Accordingly, in particular embodiments, the preview forthe connector may display an illustration of the connector and aplurality of pins found on the connector. Here, each of the pins may beselectable by the user to generate a preview for the pin. Therefore, inthis example, the wiring module may determine whether input has beenreceived indicating the user has selected a particular pin displayed inthe illustration for the connector in Operation 5023. If the user hasselected a particular pin, then the wiring module generates and providesa preview for the pin for display in Operations 5024 and 5025. Again,the preview for the pin may be configured in the same manner as thepreview for the wire and/or component. In addition, the pin may behighlighted in the illustration of the connector to help the user tobetter identify where the pin is located within the connector. This maybe quite useful to an individual who is working in the field on theparticular connector.

In some embodiments, the user may also be provided with a selectionmechanism (e.g., a button) to generate a list of the components found inthe electrical schematic of the wiring configuration displayed on thewindow. Each of the components may be identified by a referencedesignator (e.g., ResDef). Therefore, in these particular embodiments,the wiring module determines whether input has been received indicatingthe user has selected this selection mechanism in Operation 5030. If so,then the wiring module retrieves and provides the list of components fordisplay in Operations 5031 and 5032. For example, in particularembodiments, the wiring module may cause the list of components to bedisplayed in a first view pane on the window while continuing to displaythe illustration of the electrical schematic in a second view pane onthe window.

In addition, the components provided in the list may be selectable(e.g., may be displayed as a hyperlink and/or displayed with a selectionmechanism such as a button) to allow the user to view information forthe component. For example, in particular embodiments, the informationmay be displayed on a separate window and may provide a list of otherelectrical schematics found in the wiring data for the technicaldocumentation on the item in which the component is shown. Therefore,upon displaying the list of components, the wiring module may determinewhether input has been received indicating the user has selected aparticular component found in the list in Operation 5033. If the userhas selected a component found in the list, then the wiring moduleretrieves and provides the information providing the other electricalschematics in which the component is shown in Operations 5034 and 5035.In particular instances, the electrical schematics displayed in the listmay also be selectable to allow the user to retrieve and view theschematic.

FIG. 51A provides an example of a window displaying an electricalschematic of a Wiling configuration used for an item. Here, the user hasselected a particular wire 5100 shown in the schematic to generate anddisplay a preview window 5110 for the wire superimposed over the windowdisplaying the electrical schematic according to various embodiments. Inaddition, the tracing of the wire has been highlighted in the electricalschematic.

FIG. 51B provides an example of a preview window 5115 for a connectoraccording to various embodiments as a result of the user selecting theconnector 5120 in the electrical schematic. In this example, the previewwindow 5115 is superimposed over the window displaying the electricalschematic and provides an illustration of the connector (e.g., plug)displaying a plurality of pins found in the connector. Accordingly, theuser has selected a particular pin 5125 and as a result, a previewwindow 5130 for the pin has been generated and displayed. In addition,the pin 5125 has been highlighted in the illustration of the connector.

FIG. 51C provides an example of a list of components found in theelectrical schematic that has been generated and provided in a firstview pane 5135 displayed on a window according to various embodiments.In this particular example, the electrical schematic continues to beprovided in a second view pane 5140 displayed on the window. Finally,FIG. 51D provides an example of a list of other electrical schematics5145 in which a selected component is shown that has been generated anddisplayed according to various embodiments. In this example, each of theschematics (and accompanying data modules) have been made selectable toallow the user to retrieve and view a schematic if desired.

Live Wire Module

Turning now to FIG. 52 , additional details are provided regarding aprocess flow for providing live wire for a selected wire according tovarious embodiments. FIG. 52 is a flow diagram showing a live wiremodule for performing such functionality according to variousembodiments of the disclosure. In particular embodiments, the live wiremodule may be invoked by another module to provide live wire such as,for example, the wiring module previously described. However, with thatsaid, the live wire module may not necessarily be invoked by anothermodule and may execute as a stand-alone module in other embodiments.

As previously discussed, a user may select a particular wire in anelectrical schematic being displayed on a window using a particularselection mechanism (e.g., alt-clicking on the wire) and as a result,the wiring module may invoke the live wire module. Accordingly, theprocess flow 5200 begins with the live wire module generating a wirediagram displaying all of the terminal ends for the selected wire andproviding the wire diagram for display in Operations 5210 and 5215. Forinstance, the live wire module may provide the diagram in a separatewindow or in a view pane displayed on an existing window.

Accordingly, in particular embodiments, each portion of the wire shownbetween two terminal ends is selectable (e.g., displayed as a hyperlinkand/or displayed with a selection mechanism such as a button) in thewire diagram. Therefore, in these embodiments, the live wire moduledetermines whether input has been received indicating the user hasselected a portion of the wire in the diagram in Operation 5220. If so,then the live wire module provides information on the portion of thewire and the two terminal ends for display in Operations 5225. Here,depending on the embodiment, the information on the portion of the wiremay be provided on a view pane displayed on the window displaying thewire diagram (with the wire diagram displayed on a separate view pane)or on a separate window.

Here, the information displayed on the portion of the wire may includesuch information as the material used for the wiring, properties for theportion of wire, the parts (e.g., part names and/or numbers) that areassociated with the wire and/or terminals ends, location identifiers forthe terminal ends, and/or the like. Accordingly, some of the informationdisplayed for the portion of the wire may be selectable (e.g., displayedas a hyperlink and/or displayed with a selection mechanism such as abutton) to allow further information to be displayed. For example, insome embodiments, the parts (e.g., the part names and/or numbers) areselectable, as well as the location identifiers for the terminals ends.

Therefore, in these particular embodiments, the live wire moduledetermines whether input has been received indicating the user hasselected one of the parts in Operation 5230. If so, then the live wiremodule generates and provides a preview for the part for display inOperations 5235 and 5240. Similar to other previews, the part previewmay be provided as a separate window than the window displaying wilingdiagram. In some embodiments, the preview window may be superimposedover a portion of the window displaying the wiring diagram. Here, thelive wire module may retrieve the information displayed for the previewfrom the parts data (e.g., parts data modules) found in the technicaldocumentation on the item. In addition, the preview may provideinteractive functionality such as a selection mechanism to enable theuser to order the part from the IETM (as previously discussed).

Likewise, the live wire module determines whether input has beenreceived indicating the user has selected one of the locationidentifiers for a terminal end displayed on the wire window in Operation5245. If so, then the live wire module generates and provides a previewfor the location for display in Operations 5250 and 5255. Similar toother previews, the location preview may be provided as a separatewindow than the window displaying wiring diagram. In some embodiments,the preview window may be superimposed over a portion of the windowdisplaying the wiring diagram. Accordingly, the preview may provideinformation on the location of the terminal end. The live wire modulemay retrieve such information from the wiring data (e.g., wire datamodules) found in the terminal documentation of the item.

At this point, the live wire module may determine whether input has beenreceived indicating the user would like to exist from viewing the wirediagram in Operation 5265. If not, then the live wire module continuesto monitor the user's interactions. Otherwise, the live wire moduleexits.

FIG. 53 provides an example of a wire diagram generated and displayedfor a selected wire according to various embodiments. In this example,the user who is viewing the diagram has selection a portion of the wire5300 between two terminal ends 5310, 5315 that is highlighted and as aresult, information of the portion of the wire is displayed thatprovides information of the portion of the wire 5300 and the twoterminal ends 5310, 5315. Here, the parts (e.g., part numbers) andlocation identifiers (e.g. zones) are displayed as selectable (e.g.,hyperlinks) to enable the user to select a part or a location identifierfor a terminal end to generate previews providing information on thepart or the location for the terminal end.

Crosshairs Module

In particular instances, a user may be viewing an illustration for atopic displayed on a window that provides a graph. Turning now to FIG.54 , additional details are provided regarding a process flow forplacing crosshairs on the graph according to various embodiments. FIG.54 is a flow diagram showing a crosshairs module for performing suchfunctionality according to various embodiments of the disclosure. Inthis particular instance, the crosshairs module may be invoked as aresult of a user who is viewing the graph invoking a mechanism (e.g.,alt-click) to place crosshairs on the graph.

Therefore, the process flow 5400 begins with the crosshairs moduledetermining whether input has been received identifying a location toplace the crosshairs on the graph in Operation 5410. Accordingly, invarious embodiments, the user moves a cursor over the graph displayed onthe window to a position on the graph that he or she would like to placethe crosshairs and then invokes the appropriate mechanism. Such actionidentifies the location where the crosshairs module is to place thecrosshairs. If the user has appropriately identified a location, thenthe crosshairs module causes the crosshairs to be placed on the graph atthe location in Operation 5415. FIG. 55 provides an example ofcrosshairs 5500 placed on a graph displayed on a window according tovarious embodiments. The user may use this functionality to help theuser better identify the values associated with a particular location(e.g., the values associated with a particular location on a line) onthe graph.

3D Graphics Module

Turning now to FIG. 56 , additional details are provided regarding aprocess flow for providing functionality for media content involving 3Dgraphics according to various embodiments. FIG. 56 is a flow diagramshowing a 3D graphics module for performing such functionality accordingto various embodiments of the disclosure. In particular embodiments, thegraphics module may be invoked by another module to providefunctionality for 3D graphics such as, for example, the topic modulepreviously described. However, with that said, the 3D graphics modulemay not necessarily be invoked by another module and may execute as astand-alone module in other embodiments.

As previously noted, the content displayed for a particular topic mayinclude media content. In some instances, the media content may involve3D graphics. Here, for example, the topic may involve displaying theillustrated parts data for a component of an item. Accordingly, a tableof the parts used for the component may be provided in a first view panedisplayed on a window and media content for the component may beprovided in a second view pane displayed on the window. Accordingly, inparticular embodiments, the window may be configured to display thefirst and second view panes on non-overlapping portions of the window.The parts listed in the table may be selectable in the first view paneand the media content displayed in the second view pane may be a 3Dgraphic of the component. Therefore, in particular embodiments, thetopic module may determine the media content for the topic currentlybeing displayed is a 3D graphic and as a result, the topic moduleinvokes the 3D graphics module.

Thus, the process flow 5600 begins with the 3D graphics moduledetermining whether input has been received indicating the user hasselected a part in the 3D graphic using a first selection mechanism(e.g., using his or her mouse to hover over the part in the graphic) inOperation 5610. If the user has selected the part using the firstselection mechanism, then the 3D graphics module causes the selectedpart to be displayed as highlighted in both the graphic displayed in thesecond view pane and the table displayed in the first view pane in afirst format in Operations 5611 and 5612. Accordingly, the part may behighlighted in the 3D graphic and the table using different formattingdepending on the embodiment. For example, highlighting the part may beaccomplished by formatting the part in bold, in a particular color, witha border, in a different font, any combination thereof, and/or the like.Therefore, the first format may involve displaying the part in a firstcolor (e.g., green) in the 3D graphic and displaying the part in aseparate color (e.g., blue) in the table.

If the user has not selected the part using the first selectionmechanism, then the 3D graphics module may determine whether input hasbeen received indicating the user has instead selected the part in the3D graphic using a second, different selection mechanism (e.g., clickingon the part in the graphic) in Operation 5620. If the user has selecteda part using the second selection mechanism, then the 3D graphics modulecauses the selected part to be displayed as highlighted in both thegraphic displayed in the second view pane and the table displayed in thefirst view pane in a second format in Operations 5621 and 5622. Forexample, the second format may involve displaying the part in a secondcolor (e.g., blue) in the 3D graphic and displaying the part in theseparate color (e.g., blue) along with a border in the table.

In various embodiments, the first selection mechanism (e.g., hoveringover the part in the 3D graphic using a cursor) is to provide the userwith a quick way in identifying the part in the table of parts. Suchfunctionality may allow the user to move freely from part to part in the3D graphic and identify the part he or she is specifically looking forby viewing what corresponding part is highlighted in the table.Therefore, as the user moves from part to part using the first selectionmechanism, the corresponding part highlighted in the table also moves.While the previous part selected using the first selection mechanism isno longer highlighted in particular embodiments.

The second selection mechanism (e.g., clicking on the part in the 3dgraphic) is to provide the user with a way to select a part in the tablethat stays selected. For example, the user may want to view moreinformation on a part that is available through the table and/or orderthe part using a mechanism (e.g., a button) provided along with the partin the table. Therefore, in this example, the user uses the secondselection mechanism (e.g., clicking on the part in the 3D graphic) toselect the corresponding part in the table. Here, the part staysselected even after the user moves his or her cursor off the part in the3D graphic. In some embodiments; the user can select multiple parts byusing the second selection mechanism.

In some instances, the user may wish to remove a part from being viewedin the 3D graphic so that he or she can view the remaining parts of thecomponent better in the graphic. Therefore, in particular embodiments,the 3D graphics module determines whether input has been receivedindicating the user has selected a part to delete (e.g., using aselection mechanism such as right clicking on the part and selectingdelete) in Operation 5623. If so, the 3D graphics module causes the partto be removed from being displayed in the 3D graphic in Operation 5624.Accordingly, a deleted part can be added back to the 3D graphic in someembodiments. Therefore, the 3D graphics module determines whether inputhas been received indicating the user wants to un-delete a part that hasbeen removed from display in the 3D graphic in Operation 5625. If so,then the 3D graphics module causes the part to be displayed again in the3D graphic in Operation 5626.

The 3D graphics module may be configured in various embodiments to allowfor similar functionality based at least in part on the user selecting apart in the table. Therefore, the 3D graphics module may determinewhether input has been received indicating the user has selected a partin the table in Operation 5630. If so, then the 3D graphics modulecauses the part to be displayed as highlighted in the 3D graphic inOperation 5631. In addition, in particular embodiments, the 3D graphicsmodule causes the part to be zoomed in on and rotated in the 3D graphicin Operation 5632. In these particular embodiments, the 3D graphicsmodule may be configured to cause the part to be zoomed in on in the 3Dgraphic with respect to the size of the part. The smaller the part, themore the part is zoomed in on in the 3D graphic. Likewise, the 3Dgraphics module may be configured to cause the part to be rotated to abetter angle for viewing.

Although not shown in FIG. 56 , in some embodiments multiple selectionmechanisms can be used in a similar fashion to select a part in thetable as selecting a part in the 3D graphic. That is to say someembodiments may be configured to allow a user to use a first selectionmechanism (e.g. hover over a part in the table) to highlight the part ina first format and use a second, different mechanism click on the partin the table) to highlight the part in a second format.

In addition to removing parts from being displaying in the 3D graphic,parts may also be solely displayed in the 3D graphic in someembodiments. Therefore, the 3D graphics module may determine whetherinput has been received indicating the user has selected a party todisplay by itself in the 3D graphic (e.g., using a selection mechanismsuch as alt-clicking on the part) in Operation 5640. If so, then the 3Dgraphics module causes all the other parts of the component to beremoved from being displayed in the 3D graphic in Operation 5641.

Finally, in particular embodiments, the user may be providedfunctionality to display an axis or axes in the 3D graphic to assist theuser in rotating the graphic to obtain a better view of a part.Therefore, in these particular embodiments, the 3D graphics moduledetermines whether input has been received indicating the user hasselected to display the axis or axes in the 3D graphic (e.g., hasselected an add axis/axes mechanism) in Operation 5650. If so, then the3D graphics module causes display of the axis or axes in Operation 5651.

MG. 57A provides an example of a window displaying a table of parts fora component in a first view pane and a 3D graphic of the component in asecond view pane. In this example, a user has selected a particular part5700 in the 3D graphic using a first selection mechanism (e.g., by usinghis or her mouse to hover over the part) and a result, the part is 5700is highlighted in the 3D graphic and the corresponding part 5710 ishighlighted in the table according to various embodiments. Here, bothare highlighted using a first format involving showing the parts 5700,5710 in color.

FIG. 57B again provides the window displaying the table of parts for thecomponent in the first view pane and the 3D graphic of the component inthe second view pane. However, the user has now selected the particularpart 5700 in the 3D graphic using a second selection mechanism (e.g., byclicking on the part) and as a result, the part 5700 is highlighted inthe 3D graphic and the corresponding part 5710 is highlighted in thetable using a second format involving showing the parts 5700, 5710 incolor and placing a border around the part 5710 in the table accordingto various embodiments. As previously explained, the first selectionmechanism can allow the user to quickly identify where a part displayedin the 3D graphic is found in the table, while the second selectionmechanism can allow the user to actually select a part in both the 3Dgraphic and the table so that he or she may view further information onthe part and/or perform some type of functionality with respect to thepart.

MG. 57C again provides the window displaying the table of parts for thecomponent in the first view pane and the 3D graphic of the component inthe second view pane. In this example, the user is interested in a part5715 listed in the table that is also shown in the 3D graphic 5720 andselects the part 5715 (e.g., clicks on the part 5715) in the table. As aresult, the part 5715 is highlighted in the table and is highlighted inthe 3D graphic 5720 according to various embodiments as shown in FIG.57D. In addition, the part 5720 shown in the 3D graphic is zoomed in onand rotated so that the user can get a better view of the part 5720.

FIG. 57E provides an example of a 3D graphic where the user isinterested in viewing a specific part 5725 that the user has selectedbut would like to do so without the other part 5730 hindering the view.Therefore, in this example, the user selects the other part 5730 andprovides an indication to remove the part from view in the 3D graphicaccording to various embodiments. As a result, the other part 5730 isremoved from the 3D graphic so that only the part of the user isinterested in viewing 5725 is provided in the 3D graphic as shown inFIG. 57F.

FIG. 57G provides an example of a 3D graphic where the user is againinterested in viewing a specific part 5735 but would like to do sowithout the other parts shown in the graphic hindering the view. In thisexample, the user selects the specific part 5735 and indicates tosolely, show the part 5735 in the 3D graphic according to variousembodiments. As a result, the specific part 5735 is shown in the 3Dgraphic by itself without the other parts of the component beingdisplayed as shown in FIG. 57H.

Finally, FIG. 57I provides an example where the user has indicated todisplay axes 5740 in the 3D graphic according to various embodiments. Aspreviously mentioned, the user may display the axes 5740 to assist himor her in rotating the graphic to obtain a better view of a part.

Hierarchy Module

Turning now to FIG. 58 , additional details are provided regarding aprocess flow for displaying components in media content as identified ina hierarchy according to various embodiments. FIG. 58 is a flow diagramshowing a hierarchy module for performing such functionality accordingto various embodiments of the disclosure. In particular embodiments, thehierarchy module may be invoked as a result of a user indicating to viewthe hierarchy associated with the components shown in media contentcurrently being displayed. Here, the hierarchy refers to therelationships between the components of an item with respect tofunctional and/or physical breakdown of the components (e.g., breakdowninto assembly, sub-assembly, sub-sub-assembly, system, sub-system,sub-sub-system, subject, unit, part, and/or the like).

Therefore, the process flow 5800 begins with the hierarchy moduleproviding the hierarchy for the components shown in the media contentcurrently being displayed in Operation 5810. Here, in particularembodiments, the hierarchy may be provided in a first view panedisplayed on a window and the media content (e.g., illustration) may beprovided on a second view pane displayed on the window. Accordingly, inparticular embodiments, the window may be configured to display thefirst and second view panes on non-overlapping portions of the window.In addition, each of the components provided in the hierarchy may beassociated with a selection mechanism (e.g., a checkbox control) toallow the user to identify which of the components to display in themedia content and which of the components not to display.

Thus, the hierarchy module determines whether input has been receivedindicating a selection of a component to display in the media content inOperation 5815. If so, then the hierarchy module causes display of thecomponent in the media content in Operation 5820. Likewise, thehierarchy module determines whether input has been received indicating aselection of a component not to display in the media content inOperation 5825. If so, then the hierarchy module causes the component tobe removed from being displayed in the media content in Operation 5830.

In particular embodiments, a report may also be provided on thosecomponents illustrated (shown) in the media content but not listed(e.g., not found in the hierarchy). In these particular embodiments,some type of selection mechanism (e.g., a button) may be provided thatthe user can select to view the report. For example, the report may beprovided on a window that is displayed as a result of the userindicating he or she would like to view the report. Therefore, thehierarchy module may determine whether input has been receivedindicating the user would like to view the report in Operation 5835. Ifso, then the hierarchy module provides the report for display inOperation 5840. Such a report may be useful in identifying content inthe technical documentation (e.g., illustrated parts data and/orbreakdown) for the item that is deficient with respect to certaincomponents.

The hierarchy module then determines whether input has been receivedindicating the user would like to exit in Operation 5845. If so, thenthe hierarchy module causes the window to close and exits. Otherwise,the hierarchy module continues to monitor the user's interactions.

FIG. 59A provides an example of a window in which a hierarchy ofcomponents 5900 is displayed in a first view pane for the componentsshown in media content, in this instance a 3D graphic 5910, displayed ina second view pane. In this example, each of the components listed inthe hierarchy is provided with a checkbox control 5915 to allow the userto identify which of the components to display in the content media andwhich of the components not to display in the content media. FIG. 59Bprovides an example of a report 5920 of components illustrated in themedia content but not listed in the hierarchy.

Communication Session Module

Various embodiments of the IETM provide functionality to allow users toconduct communication sessions between one another within the IETMenvironment. For instance, a communication session may be a voice call,a video call, a chat session, a text session, and/or the like. Suchfunctionality allows for users to converse and interactive with eachother while in a secure environment facilitated by the IETM in manyinstances. For example, a user may be performing a maintenance task andmay have a question as to a particular step in the task. Here, thecommunication session functionality provided in various embodimentsenables the user to conduct a communication session (e.g., a voice call)and converse with another user who is actively signed into the IETM todiscuss the step of the maintenance task. Because both users are signedinto the IETM and the IETM is facilitating the session, the conversationbetween the users is secure.

Turning now to FIG. 60 , additional details are provided regarding aprocess flow for providing communication session functionality in anIETM according to various embodiments. FIG. 60 is a flow diagram showinga communication session module for performing such functionalityaccording to various embodiments of the disclosure. In particularembodiments, the communications session module may be invoked as aresult of a user who is signed into the IETM indicating he or she wouldlike to initiate a communication session with another user who isactively signed into the IETM.

The process flow 6000 begins with the communication session moduleidentifying the users who are actively signed into the IETM in Operation6010. In some embodiments, the users who are identified as active may bebased at least in part on the credentials of the user who wants toinitiate the communication session. For example, the user may be signedinto a particular object (e.g., a particular aircraft) of an item (e.g.,a type of aircraft) and therefore, the active users who are identifiedmay be those users who are currently signed into the same object (e.g.,the same aircraft). Further, in particular embodiments, other users(e.g., special users) may be identified as well such as the user'ssupervisor, quality assurance, engineering, and/or the like. Onceidentified, the communication session module provides the active users(e.g., identifiers for the active users) for display on a window inOperation 6015.

At this point, the user may select one or more of the active usersand/or special users on the window to initiate a communication sessionto. Here, the window may provide some type of selection mechanism foreach user such as a button so that the user is selectable. Therefore,the communication session module determines whether input has beenreceived indicating the user has selected a particular user in Operation6020. In addition, the user may identify the type of session he or shewould like to initiate to the user (e.g., voice call). Therefore, thecommunication session module may determine the type of communicationsession from the input as well. If the user has identified a particularuser (and the type of session), then the communication session moduleinitiates the communication session to the particular user in Operation6025.

In particular embodiments, the communication session is conducted overan IP-based network that the user's computing entity 110 is incommunication with to ensure the session is conducted over a securenetwork. Accordingly, the particular user may accept the communicationsession within the IETM. Here, the particular user may receive some typeof notification in the IETM about the incoming communication session andmay be provided with some type of selection mechanism to accept thesession.

Therefore, the communication session module determines whether input hasbeen received indicating the communication session has been accepted inOperation 6030. If the session has not been timely accepted, then theuser who initiated the communication session may decide to drop thesession. Therefore, if the session has not been accepted, then thecommunication session module determines whether input has been receivedindicating the user who initiated the session has decided to drop thesession in Operation 6035. If not, then the communication session modulemaintains the session and waits for an acceptance.

Once the communication session has been accepted, the communicationsession module determines whether input has been received indicating theuser may want to initiate a session with an additional user in Operation6040. In other words, the communication session module determineswhether the user may want to conduct a conference session involvingmultiple users. If so, then the communication session module returns toOperation 6015 and provides the available users so that the user canselect another user to include in the session. Accordingly, thecommunication session module performs the same operations to initiate acommunication session to the newly selected user and bridges the sessiononto the session with the first selected user when accepted.

Once all of the users who have agreed to be a part of the session haveaccepted, the communication session module facilities the communicationsession within the IETM environment and provides a session window fordisplay in Operation 6045. Depending on the embodiment, the sessionwindow may provide video if a communication session supporting such isbeing conducted between the users. In addition, the session window mayprovide the user with functionality such as ability to share the user'sscreen with the other users, enable a webcam, mute and/or unmute amicrophone, end the session, record, and/or the like. Therefore, theuser may then converse and interact with the other users on thecommunication session via the session window.

While the user is conversing and interacting with the other users, thecommunication session module may determine whether input has beenreceived indicating the user has selected any of the providedfunctionality. For instance, the communication session module maydetermine whether the user has decided to share his or her computingentity's screen display in Operation 6050. If so, then the communicationsession module shares the user's screen with the other users inOperation 6055. Accordingly, the communication session module maydetermine whether the user wants to use other functionality that isavailable and if so, invokes such functionality.

Finally, the communication session module determines whether input hasbeen received indicating the user wants to end the communication session(e.g., hang up the call) in Operation 6060. If so, then thecommunication session module ends the communication session in Operation6065. The communication session module then determines whether input hasbeen received indicating the user wants to close the communicationsession functionality in Operation 6070. If so, then the communicationsession module causes the session window to close and exits. It is notedthat in some embodiments upon completion of the communication session,the communication session module may save a record of the session in alog within the IETM for reporting and/or tracking purposes.

FIG. 61A provides an example of a window that provides a selectionmechanism (e.g., a button) 6100 to enable a user to access thecommunication session functionality according to various embodiments.FIG. 61B provides an example of a window 6110 according to variousembodiments that is opened as a result of the user selecting themechanism 6100. In this example, the window 6110 provides a list ofactive users 6115 and a list of special users 6120 along with aselection mechanism to allow the user to initiate a communicationsession (e.g., “call”) with one of the active users 6115 and/or specialusers 6120. In this instance, the selection mechanisms for the specialusers 6120 are unavailable indicating either the user who is initiatingthe session does not have the credentials to initiate a session any ofthe special users and/or each of the special users is not activelysigned into the IETM.

FIG. 61C provides an example of a session window 6125 that is displayedonce a communication session is activated according to variousembodiments. As shown in FIG. 61C, the session window 6125 includesdifferent functionality the user may invoke while engaged in thecommunication session. For example, the session window 6125 includes aselection mechanism (e.g., a button) 6130 that the user may select toshare his or her screen with the other users on the session. Inaddition, the session window 6625 provides a selection mechanism (e.g.,a button) 6135 to allow the user to end the communication session.Finally, FIG. 61D shows the session window 6125 once the user has sharedhis or her screen 6140 with the other users on the session.

Virtual Caution Panel Module

Various embodiments of the IETM provide a virtual caution panel thatmimics a caution panel found on an item (e.g., a piece of equipment)such as, for example, an aircraft. Therefore, turning now to FIG. 62 ,additional details are provided regarding a process flow for addressingwarnings and/or cautions provided by a caution panel found on an itemaccording to various embodiments. FIG. 62 is a flow diagram showing avirtual caution panel module for performing such functionality accordingto various embodiments of the disclosure. In particular embodiments, thevirtual caution panel module may be invoked as a result of a user who issigned into the IETM opening the virtual caution panel displayed on awindow.

Caution panels are often used to warn and/or caution personnel of aproblem with the item. Typically, personnel who are working on and/orusing the item will reference some manual, often in paper form, thatwill provide instructions on how to handle the warning and/or caution.However, time may be essence when addressing such warnings and/orcautions. For instance, returning to the example of an aircraft, acaution panel is often provided in the cockpit of the aircraft toprovide the pilot with warnings and/or cautions. When the panel providesa warning and/or caution, oftentimes the pilot may have a limited amountof time to address the problem before it becomes too late to fix whilein flight. This can lead to lose of the aircraft and/or life.Furthermore, many problems can lead to multiple warnings and/or cautionsbeing displayed. Therefore, the pilot may not only have to deal withresolving a warning and/or caution but a combination of warnings and/orcautions.

Accordingly, various embodiments provide a virtual caution panel thatcan be used by a user to assist the user in addressing warnings and/orcautions provided by such a caution panel found on an item. Theseembodiments can enable a user in addressing a warning and/or caution (orcombination thereof) in a timely manner that is not typically possibleusing a conventional manual, even when the manual may be in a digitalformat. In particular embodiments, the virtual caution panel mimics theactual caution panel found on the item with the same warnings and/orcautions.

For example, the caution panel may include a plurality of indicators(e.g., warning lights) for the different warnings and/or cautions thatlight up. These indicators may provide different levels of warningsand/or cautions, such as different color lights, to represent degrees ofurgency. Yellow may represent a caution with respect to thecorresponding component, condition, process, and/or the like for anindicator and red may represent a warning that requires more urgency inaddressing. Therefore, the user mimics the warnings and/or cautionsshown on the actual panel by selecting the same warnings and/or cautionsdisplayed on the virtual panel.

The process flow 6200 begins with the virtual caution panel moduleproviding the virtual caution panel for display on a window in Operation6210. The virtual caution panel module then determines whether input hasbeen received indicating the user has selected any of the warningsand/or cautions displayed on the virtual panel in Operation 6215.Accordingly, in particular embodiments, the virtual caution panel may beconfigured to allow the user to select different levels (e.g., setdifferent colors) for the individual indicators displayed on the panelas well as select combinations of warnings and/or cautions.

If the user has selected one or more warnings and/or cautions on thevirtual caution panel, then the virtual caution panel module retrieves acorrective action (e.g., steps to perform to address the one or morecautions and/or warnings) in Operation 6220. Therefore, in variousembodiments, the corrective actions to address the different warningsand/or cautions may be stored within the IETM and retrieved by thevirtual caution panel module based at least in part on the warningsand/or cautions (and/or combination thereof) identified by the user onthe panel. Such retrieval may be much quicker than if the user were tosearch for the corrective action him or herself in a physical and/ordigital manual. Therefore, embodiments of the virtual caution panel canbe very beneficial in addressing warnings and/or cautions in a timelymanner when required.

Once the virtual caution panel module has retrieved the correctiveaction, the module provides the corrective action for display to theuser in Operation 6225. Here, depending on the embodiment, thecorrective action may be displayed on the same window as the virtualcaution panel or displayed on a different window. The virtual cautionpanel module then determines whether input has been received indicatingthe user wishes to exit the virtual caution panel in Operation 6230. Ifso, then the virtual caution panel module causes the virtual cautionpanel to close and exits. Otherwise, the virtual caution panel modulecontinues to provide the virtual caution panel and corrective action ifappropriate.

FIG. 63A provides an example of a virtual caution panel 6300 accordingto various embodiments. In this example, an indicator 6310 has beenselected on the virtual caution panel 6300 by the user to mimic acaution being displayed by the actual caution panel found on the item. Acorrective action 6315 to address the caution may then be provided asshown in FIG. 63B.

Article Loading Module

Oftentimes entities have various items (e.g., objects for items) such asvehicles that periodically need to be loaded with different articles.For instance, many military entities have both combat and non-combatvehicles that need to be routinely loaded with different equipment. Suchvehicles may be used for air, land, and/or water and may include, forexample, aircraft, boats, ships, armored fighting vehicles,reconnaissance vehicles, light utility vehicles, engineering vehicles,self-propelled weapons and defense systems, ambulances, and/or the like.Accordingly, when such vehicles are deployed for a mission, the vehiclesare required to be carrying certain equipment expected to be used forthe mission.

For example, aircraft such as fighters and bombers and armored fightingvehicles such as tanks and troop carriers are often required to becarrying certain munitions expected to be used for combat. The loadingof these munitions is typically performed by military personnel whoreceive a list of munitions and then are required to physically load themunitions onto and/or into the vehicle. Many vehicles have multiplepositions on the vehicle for holding such munitions. For instance, manyaircraft have several positions (e.g., stations) on the body of theaircraft for holding munitions, whether they be types of weapons and/orammunitions such as missiles, bombs, and/or the like. These positionsare often configured so that only certain munitions can be placed atcertain positions.

In addition, munitions may be required to be loaded/installed on thevehicle using a number of operations (e.g., steps) and in a certainsequence. Therefore, personnel who are responsible for loading themunitions are regularly required to initially put together a workflowthat includes a number of different procedures in a sequential orderthat are to be performed to load the munitions on to the vehicle. Thegeneration of this workflow can oftentimes be very time consuming inidentifying which munitions are to be loaded at which positions,identifying the corresponding procedures for loading the munitions, andthen generating the workflow of the procedures in the correct orderedneeded to load the munitions.

Therefore, various embodiments provide functionality (e.g., articleloading wizard) that assists personnel in loading different articlesonto and/or into an object of an item. The example of loading munitionsonto an aircraft is used in discussing this functionality. However,those of ordinary skill in the art can appreciated the functionality canbe used in loading different articles for a number of different types ofitems. For example, other articles may be loaded other than equipmentsuch as cargo, personnel, perishable goods, livestock, medications,and/or the like. In addition, other items besides vehicles may be loadedsuch as warehouses, trailers, medical facilities, and/or the like.

Turning now to FIG. 64 , additional details are provided regarding aprocess flow for generating a workflow for loading articles onto and/orinto an object for an item according to various embodiments. FIG. 64 isa flow diagram showing an article loading module for performing suchfunctionality according to various embodiments of the disclosure.Accordingly, a user may be signed into the IETM for a particular objectfor an item. For example, the user may be signed into the IETM for aparticular aircraft (e.g., fighter T123) found in a military's fleet ofaircraft (fleet of jet fighters). In addition, the user may be taskedwith loading munitions onto the aircraft and therefore has also signedinto the IETM identifying a specific job to be performed. Once signedin, the user may select a mechanism to invoke the article loadingmodule.

Therefore, the process flow 6400 begins with the article loading modulereading the item the user is currently signed into the IETM to view inOperation 6410. In this instance, the item is a type of jet fighterfound in the military's fleet of aircraft. Thus, the article loadingmodule provides media content (e.g., a digital model) of the item fordisplay on a window in Operation 6415. In particular embodiments, themedia content (e.g., the digital model) displays the different loadingpositions (e.g., stations) found on the item as selectable (e.g.,associated with some type of selection mechanism). Therefore, the userselects a particular loading position by using some type of control suchas a mouse to click on, right click on, or hover over the position oruse a stylus or finger to select a position for the item.

In turn, the article loading module determines whether the user hasselected a position in Operation 6420. If so, then the article loadingmodule retrieves the articles that can be loaded at the position andprovides the articles for display on the window in Operations 6425 and6430. For example, the articles may be displayed as a list in a dropdownmenu control that is configured to allow the user to select one or moreof the articles for loading at the particular position. Note that inparticular embodiments, only those articles that can be loaded at theparticular position are retrieved and displayed to the user. Such aconfiguration can ensure that an article is not loaded by personnel atan inappropriate position.

Therefore, the article loading module determines whether input has beenreceived indicating the user has selected one or more articles for theposition in Operation 6435. If the user has selected one or morearticles, then in particular embodiments, the article loading moduleprovides media content (e.g., illustration(s) and/or image(s)) of theselected articles for display for the user to view in Operation 6440.Such an operation may be carried out in these embodiments so that theuser can see what he or she has selected to load at the position. Thismay help the user with physically selecting and loading the correctarticles in the field. Accordingly, the media content may be displayedon a separate window that is superimposed over a portion of the windowdisplaying the media content (e.g., the digital model) of the item orthe media content may be displayed on one or more view panes along withthe media content of the item on a separate view pane. In addition, thearticle loading module records the article(s) that are to be loaded atthe position in Operation 6445.

Returning to Operation 6420, if the user has not selected a particularposition for the item, then the article loading module determineswhether input has been received indicating the user's desire to generatea workflow for loading the object for the item in Operation 6450. Theuser may select some type of mechanism (e.g., a button) displayed on thewindow after the user has identified the article(s) be loaded at each ofthe positions for the item. If the user has indicated to generate theworkflow, then the article loading module generates the workflow forloading the selected article(s) onto and/or into the object for the itemin Operation 6455.

As previously noted, the workflow may include one or more procedures tobe performed by personnel in loading the article(s) onto and/or into theobject for the item. Here, the workflow may identify the sequentialorder in which the procedures are to be performed. For instance,returning to the example, the loading of munitions onto the aircraft maybe required to be carried out in a particular order to ensure the safetyof the military personnel who are physically loading the munitions ontothe aircraft. For example, certain ammunition may need to be loaded andtested before loading another ammunition to ensure the ammunition isproperly loaded and stabilized so that it will not trigger otherammunition loaded onto the aircraft from going off.

Therefore, in particular embodiments, the article loading module isconfigured to dynamically generate the workflow based on the articlesselected by the user to be loaded at each position. In some instances, asignificant number of combinations of articles can be potentially loadedat the different positions. Thus, an advantage provided by the articleloading module in some embodiments is the ability of the module todynamically generate a workflow based on a significant number ofpotential combinations that places the loading of the articles in acorrect sequence to ensure they are loaded safely.

Once the article loading module has generated the workflow, the moduleprovides the workflow for display in Operation 6460. For instance, inparticular embodiments, the article loading module may provide a digitalworkflow to be displayed in the form of a table of contents that liststhe different procedures that make up the workflow in the order in whichthey are to be performed. Here, each of the different procedures may beselectable. Therefore, the user may then select the procedures,one-by-one, in the order in which they are found in the table ofcontents to view the operations that need to be performed for theprocedures in loading the articles onto and/or into the object for theitem. As discussed in further detail herein, various functionality maybe implemented in embodiments to ensure the procedures are performed inthe correct sequence as displayed in the digital workflow.

As this point, the article loading module may determine whether inputhas been received indicating the user would like to exit in Operation6465. For example, the user may be generating a workflow for loading theobject of the item at a later time and therefore, the user may not beready to start the actual loading of the object. Here, the articleloading module may be configured to save the workflow so that is may beused at the later time.

FIG. 65A provides an example of a window displaying a digital model ofan aircraft 6500 to be loaded with articles according to variousembodiments. In this example, the digital model of the aircraft 6500displays the various positions (e.g., stations) at which articles can beloaded. Accordingly, the various stations are selectable (e.g.,displayed as hyperlinks) so that the user may select each station, suchas station 1 6510, to be provided a list (e.g., a dropdown menu control)of the different articles that may be loaded at the station. Once theuser has selected the various articles to be loaded at the differentstations, a digital workflow in the form of a table of contents 6515 maybe generated with the different procedures to be performed in loadingthe aircraft in the order in which they are to be performed as shown inFIG. 65B. A discussion is now provided with respect to using the digitalworkflow at a time when the article(s) are actually being loaded ontoand/or into the object for the item.

Loading Workflow Module

Turning now to FIG. 66 , additional details are provided regarding aprocess flow for managing a workflow for loading articles onto and/orinto an object for an item according to various embodiments. FIG. 66 isa flow diagram showing a loading workflow module for performing suchfunctionality according to various embodiments of the disclosure. Here,a digital workflow may be displayed on a window in the form of a tableof contents listing the procedures to be performed in loading thearticles onto and/or into the object for the item. As noted, theprocedures are provided in the table of contents in particularembodiments in the order in which they are to be performed in loadingthe object. Accordingly, each of the procedures found in the table ofcontents may be selectable so that the user selects the procedures oneat a time in the sequence provided to view the operations to perform forthe selected procedure to load the articles onto and/or into the objectfor the item.

Therefore, the process flow 6600 begins with the loading workflow moduledetermining whether input has been received indicating the user hasselected a procedure in the table of contents in Operation 6610. If so,then the loading workflow module determines whether the selectedprocedure is the next procedure to be performed for the workflow inOperation 6615. Therefore, in particular embodiments, that loadingworkflow module is configured to determine whether the procedure(s)found in the workflow listed before the selected procedure have beenperformed. As further discussed below, the loading workflow module marksthe procedures that have been completed in some embodiments. Therefore,the loading workflow module is able to determine whether each of theprocedures found in the workflow before the currently selected procedurehas been completed.

If each of the procedures in the workflow before the currently selectedprocedure has not been completed, then the loading workflow moduleprovide an error to the user in Operation 6620. For example, the loadingworkflow module may provide an error message for displaying on a windowinforming the user that the selected procedure is not the next procedureto be performed in the workflow. In addition, the loading workflowmodule may be configured in some embodiments so that the operations forthe selected procedure cannot be displayed.

However, if the selected procedure is the next procedure in thesequence, then the loading workflow module provides the procedure fordisplay to the user in Operation 6625. For instance, in particularembodiments, the loading workflow module may retrieve the data for theprocedure from the technical documentation for the item and provide thedata for the procedure to display on a new window for the user.Depending on the embodiment, the procedure may be displayed on a paneprovided on the window with the workflow (with the workflow displayed ona second pane) or the procedure may be provided on a separate windowfrom the window with the workflow. As a result, the user is then able toread the instructions (e.g., different operations) found in theprocedure and perform the instructions accordingly.

For instance, in the example involving the loading of munitions onto thejet fighter, the different procedures found in the workflow may involveprocedures that provide instructions for loading a particular munitionat a particular station of the aircraft, as well as procedures fortesting a munition once it has been loaded at a particular station.Therefore, the instructions for the different procedures may provide asequence of operations (e.g., steps) to be performed by the militarypersonnel who are loading munitions onto the jet fighter.

Accordingly, the loading workflow module may determine whether input hasbeen received that the end of the procedure currently being displayedhas been reached in Operation 6630, indicating the user has completedperforming the procedure. Here, the loading workflow module may beconfigured to determine the end of the procedure has been reached byreceiving input indicating the user has performed some action such as,for example, selecting a mechanism such as a button displayed on thewindow and/or scrolling to the bottom on the procedure displayed on thewindow.

If the end of the procedure has been reached, then the loading workflowmodule in various embodiments determines whether each of the operationsfound in the procedure has been acknowledged in Operation 6635. Forinstance, in some embodiments, each operation (e.g., step) found in theprocedure may be associated with a selection mechanism such as acheckbox control that the user selects to acknowledge that he or she hascompleted the particular operation in the procedure. Therefore, theloading workflow module may determine whether input has been receivedthat the selection mechanism for each operation has been selected by theuser. In addition, in some embodiments, the loading workflow module maybe configured to also determine whether the user has acknowledged eachof the previous operations in the procedure whenever the useracknowledges a particular operation in the procedure to ensure theoperations are performed in order.

If the user has not acknowledged all of the operations in the procedure,then the loading workflow module causes display an error to the user inOperation 6640. Again, the loading workflow module may provide an errormessage to display informing the user that all of the operations in theprocedure have not been acknowledged as being performed. However, if allof the operations have been acknowledged, then the loading workflowmodule marks the procedure as completed in Operation 6645. At thispoint, the loading workflow module returns to the window displaying thetable of contents for the workflow if need be in Operation 6650.Accordingly, as a result of the user completing the procedure, theloading workflow module may cause the procedure to be displayed as beingcompleted in the digital workflow (e.g., the table of contents). Forexample, in particular embodiments, the procedure may now be displayedalong with some type of indicator (e.g., in a particular font, in aparticular color, with a symbol such as a plus sign, as no longerselectable, and/or the like) to demonstrate the procedure has beencompleted. The user may then select the next procedure found in theworkflow.

Once the user has performed all of the procedures for the workflow, thenthe user may decide to exit the window displaying the table on contentsand select a mechanism (e.g., a button) displayed on the window to doso. As a result, the loading workflow module may determine input hasbeen received indicating the user would like to exit in Operation 6655.The loading workflow module then determines whether the workflow forloading the articles onto and/or into the object for the item has beencompleted in Operation 6660. That is to say, the loading workflow moduledetermines whether each of the procedures found in the workflow has beencompleted.

Accordingly, if the workflow has not been completed, then the loadingworkflow module in particular embodiments provides an error (e.g., anerror message for displaying on a window) to the user indicating theworkflow has not been completed in Operation 6665. The loading workflowmodule may then determine whether input has been received indicating theuser still wishes to exit the window displaying the digital workflow inOperation 6670. For example, the personnel who are loading the munitionsonto the jet fighter may be taking a lunch break. Therefore, the usermay wish to exit the window for security reasons while away from theloading area and eating lunch. He or she then plans to resume with theworkflow once he or she has returned from lunch.

If this is the case, then the loading workflow module in particularembodiments records one or more images of the object in Operation 6675to document the progress of loading the articles that has been completedto that point. For example, imaging devices may be installed atdifferent locations in the loading area to allow images to be taken ofthe different loading stations. In addition, the loading workflow modulerecords the progress of the workflow in a log in Operation 6680.Therefore, in the example, the user can retrieve the incomplete workflowupon returning from lunch and continue with the remainder of theworkflow for loading the munitions onto the jet fighters. Once the userhas completed the workflow, the loading workflow module again recordsimage(s) of the object to document the loading of the articles andrecords the completion of the workflow in the log.

Recordation of the images and progress of the workflows in variousembodiments can allow for tracking of the workflows being performed, aswell as allow for quality control measures to be put into place toevaluate different personnel on performing loading tasks. For example,recordation of the images of the jet fighter loaded with the requiredmunitions may allow for the pilot to view the images prior to takeoff toensure the munitions have been properly loaded onto the aircraft. Thiscan help to not only ensure success of the mission but can also ensurethe safety of the pilot and any other flight crew member on theaircraft.

Remote Device Integration Module

As previously discussed, users are oftentimes working in environmentswhere network connectivity (e.g., wireless network) for their computingentity 110 is unavailable. For instance, maintenance personnel may beworking out in the field performing maintenance on an object (e.g., anaircraft) where network connectivity is unavailable. In these instances,the maintenance personnel may be making use of the IETM to view one ormore maintenance procedures they are to perform on the object. However,one of the maintenance personnel may want to perform some type offunctionality provided by embodiments of the IETM that may requireconnectivity. For example, the maintenance personnel may want to order apart to replace a part taken from inventory used in performing themaintenance on the object. As previously noted, various embodiments canfacilitate the personnel's ordering of the part by generating agraphical code that can then be scanned by the personnel using a remotedevice such as his or her mobile device with some type of connectivelysuch as cellular.

However, security is also often a concern with allowing suchfunctionality since the functionality is being carried out over anetwork that is not within the IETM environment. Therefore, variousembodiments allow for such functionality to be carried out over anetwork connected to a remote device while still maintaining a secureenvironment. Here, a remote device is a device that is not incommunication with the user's computing entity 110 being used to accessthe IETM. For example, the remote device may be the user's mobile device(e.g., smartphone), tablet, and/or the like with connectivity to anetwork such as a cellular network, wireless network, and/or the like.Specifically, in particular embodiments, the user (e.g., maintenancepersonnel) who is signed into the IETM may have a software application(e.g., an app) installed on his or her remote device that is required tobe used to enable the functionality to be performed in the IETM. Thissoftware application may be limited in its distribution so that it isonly installed on devices belonging to valid users.

Turning now to FIG. 67 , additional details are provided regarding aprocess flow for securely integrating the use of a network connected toa remote device with the IETM according to various embodiments. FIG. 67is a flow diagram showing a remote device integration module forperforming such functionality according to various embodiments of thedisclosure. Here, the user may be signed into the IETM and decides toperform some functionality within the IETM that requires connectivitysuch as, for example, submitting a form filed out while signed into inthe IETM to a backend system. Accordingly, a selection mechanism (e.g.,a button) may be provided on the form that the user selects to submitthe form and as a result, the remote device integration module isinvoked in various embodiments.

Therefore, the process flow 6700 begins with the remote deviceintegration module generating and providing a security graphical codefor displaying in Operations 6710 and 6715. For instance, depending onthe embodiment, the security graphical code may be a barcode, a quickresponse code, a one-dimensional code, a universal product code, a datamatric code, and/or the like. In addition, in particular embodiments,the remote device integration module may generate the security graphicalcode to contain the user's credentials used in signing into the IETM.Accordingly, the security graphical code may be displayed on a window sothat the user can scan the code using some type of code reader installedon the user's mobile device.

For example, the code reader may be any one of many commerciallyavailable graphical code readers and the reader may not necessarilyinclude any type of security features. While in other instances, thesoftware application may be configured so that the application can beused initially to scan the security graphical code. However, otherfunctionality may not be available within the application. Such aconfiguration can provide security features within the softwareapplication with respect to allowing the user to perform certainfunctionality using the software application while not allowing the userto perform other functionality. In addition, the software applicationmay be configured to require the user to provide credentials (e.g., ausername and/or password) to open the application. Therefore, inparticular embodiments, various functionality provided by the softwareapplication residing on the user's remote device may become available asa result of the user scanning the security graphical code displayed inthe window.

The remote device integration module then determines whether input hasbeen received indicating to generate a graphical code for the form theuser wishes to submit in Operation 6720. For instance, the remote deviceintegration module may determine that the security graphical code hasbeen scanned by the user as a result of the user acknowledging he or shehas scanned the code. For example, the window displaying the securitygraphical code may provide a selection mechanism such as a button thatthe user can select to close the window with the code. Accordingly, theremote device integration module may receive input indicating the windowwith the security graphical code has been closed and as a result,generate and provide the graphical code for the form for display inOperations 6725 and 6730.

Again, the remote device integration module may provide the graphicalcode for the form to display on a window so that the user can now usehis or her mobile device to scan the code. Again, depending on theembodiment, the graphical code may be a quick response code, aone-dimensional graphical code, a universal product code, a data matricgraphical code, and/or the like. The graphical code may includeinformation provided by the user on the form such as the informationrequired to order the part. In addition, the graphical code may includeinformation such as the user's credentials, an identifier for the objectand/or item, an identifier for a location for the user, and/or the like.Further, the graphical code may be configured so that it can only beread by the software application residing on the user's remote device.

At this point, the remote device integration module determines whetherto exit in Operation 6735. For example, the user may have scanned thegraphical code for the form and then selected a mechanism such as abutton provided on the window displaying the code to close the window.As a result, the remote device integration module may receive inputindicating the window has been closed. If that is the case, then theremote device integration module exits.

It is noted that in some embodiments the remote device integrationmodule may be invoked at different times other than when specificfunctionality is to be carried out that requires connectivity. Forinstance, in particular embodiments, the user may invoke the remotedevice integration module upon signing into the IETM to establish thatthe software application residing on the user's remote device can thenbe used in facilitating any functionality requiring connectivity whilethe user is signed into the IETM. Therefore, in these particularembodiments, the user may not be required to scan a security graphicalcode each time he or she wishes to use functionality provided by theIETM that requires connectivity. Thus, the process flow 6700 shown inFIG. 67 may only involve providing the security graphical code withoutnecessarily providing a graphical code to facilitate otherfunctionality.

Virtual Network Module

Virtual private networks (VPNs) are often used to allow users to sendand share data over networks that are not necessarily secure (e.g.,public networks) as though they are connected to a secure privatenetwork. Accordingly, applications running over a VPN can often benefitfrom the functionality, security, and management provided in a privatenetwork. Therefore, various embodiments provide a virtual network inwhich users can operate within while signed into the IETM.

Turning now to FIG. 68 , additional details are provided regarding aprocess flow for providing a virtual network within the IETM environmentaccording to various embodiments. FIG. 68 is a flow diagram showing avirtual network module for performing such functionality according tovarious embodiments of the disclosure. Depending on the circumstances, auser may have already signed into the IETM and decides to join a virtualnetwork provided through the IETM or the user may join a virtual networkat the time when he or she signs into the IETM.

In particular embodiments, the user may have a software applicationinstalled on remote device such as his or her mobile device thatprovides a graphical code for the user to scan using his or hercomputing entity 110 (e.g., webcam on his or her computing entity 110)being employed to view the IETM. Here, the graphical code may beprovided in various forms such as a barcode, a quick response (QR) code,a one-dimensional code, a universal product code, a data matric code,and/or the like. While in other embodiments, a graphical code may beprovided on an object that is scanned by the user using his or hercomputing entity 110. For example, the user may be maintenance personalwho is working on a particular aircraft found in an airline's fleet andthe graphical code may be physically displayed on a component of theaircraft such as its landing gear.

Therefore, the user invokes the virtual network module to scan thegraphical code and the process flow 6800 begins with the virtual networkmodule scanning the graphical code in Operation 6810. The virtualnetwork module then determines whether the graphical code that has beenscanned is valid in Operation 6815. Accordingly, the virtual networkmodule is configured in various embodiments to interrogate theinformation found in the code to determine whether the code isassociated with a valid user and/or object.

For example, the graphical code that was scanned may have been providedby a software application installed on the user's mobile device. Here,the user may have signed into the application and generated the codeusing functionality provided by the application. Therefore, theinformation provided in the code may identify the user (e.g., providecredentials for the user) and the virtual network module may determinewhether the credentials provided for the user in the graphical code arevalid. While in another example, the graphical code that was scanned mayhave been provided on an object (e.g., aircraft) and the informationprovided in the code may identify the object. Therefore, the virtualnetwork module may determine whether the object identified in the codeis valid (e.g., is scheduled to have maintenance performed on theobject).

If the virtual network module determines the graphical code is invalid,then the virtual network module causes display an error message to theuser in Operation 6820. For instance, in particular embodiments, thevirtual network module may provide an error message via a windowinforming the user that the graphical code is invalid. The virtualnetwork module then determines whether input has been receivedindicating the user would like to exit or scan another graphical code inOperation 6825. For example, the window displaying the error message mayprovide a first selection mechanism (e.g., a first button) to exit and asecond selection mechanism (e.g., a second button) to scan another code.If the user indicates he or she would like to scan another code, thenthe virtual network module returns to Operation 6810.

However, if the graphical code is valid, then the virtual network modulein particular embodiments may provide one or more objects identifyingthe various virtual networks available to the user in Operation 6830.This particular operation may be carried out when the graphical codescanned by the user provides the user's credentials. Here, for example,the virtual network module may identify the objects the user iscurrently authorized to work on. For instance, the user may bemaintenance personnel who is scheduled to perform maintenance on twoparticular aircraft found in an airline's fleet. Therefore, in thisinstance, the virtual network module may identify the two aircraft asavailable to the user.

Accordingly, in various embodiments, a virtual network is configured foreach of the objects so that the user's selection of a particular objectidentifies which virtual network supported by the IETM the user is tojoin while signed into the IETM. In addition, the selection of an objectmay also identify an instance for the IETM. That is to say, theselection of the object (and corresponding virtual network) may identifywhat technical documentation to make available to the user while he orshe is signed into the IETM, as well as identify any information foundwithin the IETM for the particular object such as the maintenance jobsto be performed on the object.

Therefore, the virtual network module determines whether input has beenreceived indicating the user has selected a particular object inOperation 6835. If so, then the virtual network module joins the virtualnetwork for the object in Operation 6840. Accordingly, if the graphicalcode scanned by the user includes information that identifies theobject, then the virtual network module may automatically join thecorresponding virtual network without the user having to select theobject. This may also be true if only a single object is associated withthe user.

The user may then be provided with specific functionality as a result ofjoining the virtual network. In addition, the user may interact directlywith other users who are signed into the IETM and are on the samevirtual network. In some instances, specific functionality may beassociated with the corresponding object.

For example, many entities establish a lockout program for maintenance.A lockout program often involves “locking out” certain operations,processes, functions, and/or the like for an object that may be unsafeto perform while certain maintenance is being carried out on the object.For instance, the power supply for a particular component may be shutoff while maintenance is being performed on the component. Here, sometype of warning (e.g., a lockout tag) may be placed on the componentand/or the power supply indicating that it is unsafe to turn back on thepower so that personnel who are not performing the maintenance on thecomponent do not inadvertently restore power to the component while themaintenance is being performed.

Therefore, in various embodiments, the virtual network module may invokelockout functionality for the object in Operation 6845 that broadcastswarnings to all the users who are on the virtual network for the object.In some instances, such functionality may require the users on thevirtual network for the object to acknowledge the warnings, as well astrack which users have or have not acknowledged the warnings. Those ofordinary skill in the art can envision other object-specificfunctionality may be invoked in light of disclosure.

In addition, some of the specific functionality may be associated withthe user. For example, the user may be signed into the IETM and usingthe technical documentation to perform a specific role with respect tothe object. For instance, the user may be maintenance personnel,engineering personnel, operations personnel, and/or the like. In manyinstances, the user may have one or more tasks (e.g., jobs) that theuser is expected to perform with respect to the object while signed intothe IETM. Therefore, the virtual network module in particularembodiments may identify and/or assign and/or allocate one or more tasks(e.g., jobs) to the user to perform with respect to the object inOperation 6850. Those of ordinary skill in the art can envision otheruser-specific functionality may be invoked in light of disclosure.

It is noted that the virtual network may be provided over a variety ofdifferent types of networks such as IP-based and/or cellular dependingon the embodiment. In addition, in particular embodiments, the virtualnetwork may be facilitated through the software application installed onthe user's remote device. In these particular embodiments, the user maysign into the software application and/or the user may scan a graphicalcode displayed via the IETM or found on an object using the softwareapplication to display one or more available virtual networks forobjects or to automatically connect to a virtual network for an objectthrough the software application. Accordingly, the software applicationcan identify the user and provide what virtual networks are available tothe user. In turn, the user can select one of the available virtualnetworks and connect to the network on his or her mobile device. As aresult, the same functionality (e.g., object-specific functionalityand/or user-specific functionality) described above may be providedthrough the software application installed on the user's remote device.That is to say, the software application may be configured to performsimilar operations to those performed by the virtual network moduledescribed above in various embodiments.

Import Module

The technical documentation associated with an item (e.g., the datasetthat includes the textual information, corresponding media content, andother data that make up the technical documentation for the item) istypically stored and/or provided in accordance with S1000D standards.For example, data modules are normally provided that include headerand/or preface data in accordance with S1000D standards. S1000Dstandards require a document to be broken down into individual datamodules that are typically identified via XML and/or SGML tags, labels,and/or metadata and that are organized into a hierarchical XML and/orSGML structure. In various embodiments, the inn: and/or SGML filesand/or data stored therein may be converted to JSON formatted dataand/or files. Accordingly, in these embodiments, the content found inthe JSON formatted data and/or files provides the technicaldocumentation for the item.

However, instances may occur in which an entity may have documentationin formats that are not in accordance with S1000D standards. Forexample, many entities have technical manuals, instructions, orders,and/or the like for various items in PDF files and/or SGML files that donot adhere to S1000D standards. Therefore, these entities are oftentimesrequired to use systems, software, applications; and/or the like otherthan an IETM to view such documentation since most conventional IETMsrequire the technical documentation to adhere to S1000D standards. Thiscan lead to the entities having to maintain multiple components (e.g.,systems, software, applications, and/or the like) to view all of thetechnical documentation associated with a particular item. In addition,users who are viewing/using the documentation are then required to havethe multiple components available to them at any given time so that theyhave access to any of the documentation as needed.

Therefore, various embodiments are configured to allow the import ofsource data that does not adhere to S1000D standards into the IETM.Accordingly, such embodiments allow users to view technicaldocumentation in the IETM from data sources other than those that adhereto S1000D standards. As a result, users can view and use the completetechnical documentation for an item in many instances using a singleinstrument (the ILEUM). In addition, these embodiments eliminate theneed to convert source data in many instances in accordance with S1000Dstandards to import into the IETM.

Turning now to FIG. 69 , additional details are provided regarding aprocess flow for importing data for the technical documentation for anitem into the IETM according to various embodiments. FIG. 69 is a flowdiagram showing an import module for performing such functionalityaccording to various embodiments of the disclosure. Depending on thecircumstances, the data (e.g., dataset) may be provided in differentformats and adhere to different standards. For instance, the data may beprovided in XML and/or SGML files in accordance with S1000D standards.However, the data may also be provided in XML, SGML, PDF files and/orthe like that are not in accordance with S1000D standards. In someinstances, the data may include a combination of both types of files.

Therefore, the process flow 6900 begins with the import module receivingthe data to import in Operation 6910. Here, the data may be received inany number of different formats. For example, the data may be a datasetfor a publication of the technical documentation for an item accordingto S 1000D standards. While in another instance, the data may be one ormore files having content (e.g., manual) that make up the technicaldocumentation for the item in a file format such as PDF and/or SGML.

The import module then determines whether the data is provided inaccordance with S1000D standards in Operation 6915. For instance, inparticular embodiments, the import module may make such a determinationbased on whether the data is provided as XML and/or SGML files thatconform to data modules found in a dataset adhering to S1000D standards.If that is the case, then the import module selects one of the datamodules in Operation 6920 and converts the data module to JSON format inOperation 6925. The import module may then store the converted datamodule for use with the IETM. At this point, the import moduledetermines whether the data includes another data module in Operation6930. If so, then the import module returns to operation 6920, selectthe next data module found in the data, and preforms the operations justdescribed for the newly selected data module.

However, if the data is not provided in accordance with S1000Dstandards, then the import module selects a file found in the data inOperation 6935. As previously mentioned, the file may be provided in anynumber of different formats such as PDF, SGML, DOC, RIF, TXT, WPS,and/or the like. Therefore, the import module converts the file to JSONformat and stores the converted file in Operation 6940 in someembodiments, the import module may be configured to convert the file toJSON format in multiple steps. For example, in particular embodiments,if the original file is in TXT format; then the import module may firstconvert the file to SGML format and then convert the file to JSONformat. At this point, the import module determines whether the dataincludes another file in Operation 6945. If so, then then the importmodule returns to operation 6935, select the next file found in thedata, and preforms the operations just described for the newly selectedfile. Once the import module has processed all the files found in thedata, the import module exists.

It should be noted that the data received to be imported into the IETMin some instances may include both content in accordance with S1000Dstandards (e.g., include data modules) and content not in accordancewith S1000D standards (e.g., include files in PDF format). Therefore, inthese particular instances, the process flow 6900 may involve looking atindividual components of the data to determine how to process each ofthe individual components.

Accordingly, as a result of importing data from different sources bothadhering and not adhering to S1000D standards and converting such datato a common format (e.g., JSON), the data from the different sources(e.g., technical documentation for the different sources) can be usedinterchangeably and/or simultaneously in the IETM in variousembodiments. In addition, various embodiments are able to provide thesame functionality, security, features, and performance for all of thetechnical documentation for an item in the IETM regard of the source ofthe technical documentation. Therefore, as a result, functionality thatwould not normally be available for some technical documentation can nowbe provided for the documentation in the IETM.

For instance, a technical manual may be sourced in one or more PDFfiles. Therefore, a user would typically make use of a PDF reader (e.g.,application) to view the technical manual. A conventional PDF readerdoes not furnish the functionality implemented in various embodimentsdescribed herein. For example, a conventional PDF reader does notfurnish the preview capabilities described herein provided by variousembodiments. However, as a result of importing the PDF files for thetechnical manual as described herein, the preview capabilities may beimplemented for the technical manual in various embodiments. That is tosay, links may be provided in the content of the technical documentationoriginating from the PDF files that can be configured to generate anddisplay previews. Such links cannot normally be placed in PDF files andprovided in a PDF reader.

In addition, a PDF reader does not have the capability to allow a userto search a set of PDF files. Therefore, if the technical documentationinvolves multiple files, then the user who is using a PDF reader isrequired to open the files one at a time to search for a particular termand/or topic. However, various embodiments would allow the user tosearch the entire library (e.g., multiple PDF files) for the technicaldocumentation in the IETM with a single search.

Further, the data structure and/or formatting (e.g., number of chapters,paragraphs, figures, tables, and/or the like) may be maintained byimporting the data source that is not required to adhere to S1000Dstandards. This may be helpful to a user who needs to navigate thetechnical documentation since the structure and formatting mimic thestructure and formatting found in the original data source. Finally,personnel who maintain the data source (e.g., maintain the technicalmanual provided in the PDF file(s)) are not required to convert the datasource to another file format (e.g., XML and/or SGML) and/or to S 1000Dstandards, or learn how to do so for that matter, for embodiments thatallow source data that does not adhere to S1000D standards to beimported and used in the IETM.

Therefore, in various embodiments, when a data request is receivedwithin the IETM. For example, a user may select a component, topic,request a preview, and/or the like while signed into the IETM. The datarequest may identify particular content that was imported as a datamodule and/or data file that can be provided in JSON format.Accordingly, in some embodiments, providing the content in JSON formatmay allow the content to be transmitted and/or processed more quicklythan if the content were provided in another file format such as XML,SGML, and/or PDF format.

CONCLUSION

Many modifications and other embodiments of the disclosure set forthherein will come to mind to one skilled in the art to which thesemodifications and other embodiments pertain having the benefit of theteachings presented in the foregoing descriptions and the associateddrawings. Therefore, it is to be understood that the disclosure is notto be limited to the specific embodiments disclosed and thatmodifications and other embodiments are intended to be included withinthe scope of the appended claims. Although specific terms are employedherein, they are used in a generic and descriptive sense only and notfor purposes of limitation.

In addition, the functionality described herein involving parts may beapplicable to other components in various embodiments. For instance, thefunctionality involving 3D graphics is described herein with respect toviewing different parts used for a component of an item in a 3D graphic.Those of ordinary skill in the art will recognize that suchfunctionality may be applicable in various embodiments with respect toviewing other components in addition to parts. As previously noted,components may identify functional and/or physical structures of an itemand may be broken down into assembly, sub-assembly, sub-sub-assembly,system, sub-system, sub-sub-system, subject, unit, part, and/or thelike. Therefore, a 3D graphic may not only be provided at the partlevel, but may be provided at other levels found within the structure ofthe item and therefore, the functionality described herein with respectto 3D graphics may be applicable to these other levels and correspondingcomponents. The same can be said with respect to other functionalitydescribed herein involving parts such as generating a preview for apart. Therefore, it should be understood the functionality describedherein involving parts is not to be limited to use with just parts andmay be used with respect to other components of an item in variousembodiments.

1. A method for generating an annotation for at least one of textualinformation or a graphical image for technical documentation for an itemin an interactive electronic technical manual system (IETM) configuredto provide electronic and credentialed access to the technicaldocumentation for the item, the method comprising: providing a firstsign-in window for display, the first sign-in window comprising anelectronic form via a first IETM viewer executing on a first usercomputing entity being used by a first user signed into the IETM,wherein (a) the first user provides (i) input of a selection of adataset corresponding to the technical documentation for one of the oneor more items, (ii) input of a selection of a unit displayed for theselectable unit field, and (iii) input of a selection of an objectdisplayed for the selectable object field, and (b) a sign-in mechanismauthenticates and signs the first user into the IETM based at least inpart on a first user credential, the dataset, the selection of the unitdisplayed, and the selection of the object displayed; providing a secondsign-in window for display, the second sign-in window comprising anelectronic form via a second IETM viewer executing on a second usercomputing entity being used by a second user signed into the IETM,wherein (a) the second user provides (i) input of a selection of adataset corresponding to the technical documentation for one of the oneor more items, (ii) input of a selection of a unit displayed for theselectable unit field, and (iii) input of a selection of an objectdisplayed for the selectable object field, and (b) a sign-in mechanismauthenticates and signs the second user into the IETM based at least inpart on a second user credential, the dataset, the selection of the unitdisplayed, and the selection of the object displayed; providing an ITEMwindow for display via the first IETM viewer executing on the first usercomputing entity, the ITEM window displaying at least one of the textualinformation or a graphical image; receiving input of a selection of anannotation selection mechanism provided via the ITEM window; andresponsive to receiving the input of the selection of the annotationselection mechanism provided via the IETM window, providing anannotation window, for annotating at least one of the textualinformation or the graphical image, wherein the annotation windowcomprises at least one of an attach file mechanism, an image capturemechanism, a share mechanism, or a change request mechanism; receivinginput of a selection of the change form mechanism, wherein the selectionof the change form mechanism is performed by the first user via thefirst IETM viewer; and responsive to receiving the input of theselection of the change form mechanism: providing an electronic changeform comprising a plurality of fields for display via the first IETMviewer; pre-populating at least one field of the plurality of fields onthe electronic change form based at least in part on informationprovided in the annotation; and submitting a request for change to atleast one of the textual information or the graphical image based atleast in part on information provided on the change form.
 2. The methodof claim 1, wherein the annotation window further comprises a freeformfield configured to allow the user to enter a comment recorded for theannotation.
 3. The method of claim 1 further comprising recording a dateand a time when the annotation was generated along with the annotation.4. The method of claim 1, wherein responsive to receiving the input ofthe selection of the change form mechanism, the method further comprisesattaching at least one of the file and the image to the request forchange.
 5. The method of claim 1 further comprising: receiving input ofa selection of a mechanism to view a list of annotations, wherein theselection of the mechanism to view the list of annotation is performedby the first user via the first IETM viewer; and responsive to receivingthe selection of the mechanism to view the list of annotations:generating a list of annotations window comprising the list ofannotations comprising the annotation for at least one of the textualinformation or the graphical image; and providing the list ofannotations window for display via the first IETM viewer, wherein thelist of annotations comprises annotations created by the first user thelist of annotations window is configured to allow the user to select anannotation found in the list of annotations to view.
 6. An apparatus forgenerating an annotation for at least one of textual information or agraphical image for technical documentation for an item in aninteractive electronic technical manual system (IETM) configured toprovide electronic and credentialed access to the technicaldocumentation for the item, the apparatus comprising at least oneprocessor and at least one memory including a computer program code, theat least one memory and the computer program code configured to, withthe at least one processor, cause the apparatus to: provide a firstsign-in window for display, the first sign-in window comprising anelectronic form via a first IETM viewer executing on a first usercomputing entity being used by a first user signed into the IETM,wherein (a) the first user provides (i) input of a selection of adataset corresponding to the technical documentation for one of the oneor more items, (ii) input of a selection of a unit displayed for theselectable unit field, and (iii) input of a selection of an objectdisplayed for the selectable object field, and (b) a sign-in mechanismauthenticates and signs the first user into the IETM based at least inpart on a first user credential, the dataset, the selection of the unitdisplayed, and the selection of the object displayed; provide a secondsign-in window for display, the second sign-in window comprising anelectronic form via a second IETM viewer executing on a second usercomputing entity being used by a second user signed into the IETM,wherein (a) the second user provides (i) input of a selection of adataset corresponding to the technical documentation for one of the oneor more items, (ii) input of a selection of a unit displayed for theselectable unit field, and (iii) input of a selection of an objectdisplayed for the selectable object field, and (b) a sign-in mechanismauthenticates and signs the second user into the IETM based at least inpart on a second user credential, the dataset, the selection of the unitdisplayed, and the selection of the object displayed; provide an ITEMwindow for display via the first IETM viewer executing on the first usercomputing entity, the ITEM window displaying at least one of the textualinformation or a graphical image; receive input of a selection of anannotation selection mechanism provided via the ITEM window; andresponsive to receiving the input of the selection of the annotationselection mechanism provided via the IETM window, provide an annotationwindow, for annotating at least one of the textual information or thegraphical image, wherein the annotation window comprises at least one ofan attach file mechanism, an image capture mechanism, a share mechanism,or a change request mechanism; receive input of a selection of thechange form mechanism, wherein the selection of the change formmechanism is performed by the first user via the first IETM viewer; andresponsive to receiving the input of the selection of the change formmechanism: provide an electronic change form comprising a plurality offields for display via the first IETM viewer; pre-populate at least onefield of the plurality of fields on the electronic change form based atleast in part on information provided in the annotation; and submit arequest for change to at least one of the textual information or thegraphical image based at least in part on information provided on thechange form.
 7. The apparatus of claim 6, wherein the annotation windowfurther comprises a freeform field configured to allow the user to entera comment recorded for the annotation.
 8. The apparatus of claim 6,wherein the at least one memory and the computer program code areconfigured to, with the at least one processor, cause the apparatus torecord a date and a time when the annotation was generated along withthe annotation.
 9. The apparatus of claim 6, wherein responsive toreceiving the input of the selection of the change form mechanism, theat least one memory and the computer program code are configured to,with the at least one processor, cause the apparatus to attach at leastone of the file and the image to the request for change.
 10. Theapparatus of claim 6, wherein the at least one memory and the computerprogram code are configured to, with the at least one processor, causethe apparatus to: receive input of a selection of a mechanism to view alist of annotations, wherein the selection of the mechanism to view thelist of annotation is performed by the first user via the first IETMviewer; and responsive to receiving the selection of the mechanism toview the list of annotations: generate a list of annotations windowcomprising the list of annotations comprising the annotation for atleast one of the textual information or the graphical image; and providethe list of annotations window for display via the first IETM viewer,wherein the list of annotations comprises annotations created by thefirst user the list of annotations window is configured to allow theuser to select an annotation found in the list of annotations to view.11. A non-transitory computer storage medium comprising instructionsapparatus for generating an annotation for at least one of textualinformation or a graphical image for technical documentation for an itemin an interactive electronic technical manual system (IETM) configuredto provide electronic and credentialed access to the technicaldocumentation for the item, the instructions being configured to causeone or more processors to at least perform operations configured to:provide a first sign-in window for display, the first sign-in windowcomprising an electronic form via a first IETM viewer executing on afirst user computing entity being used by a first user signed into theIETM, wherein (a) the first user provides (i) input of a selection of adataset corresponding to the technical documentation for one of the oneor more items, (ii) input of a selection of a unit displayed for theselectable unit field, and (iii) input of a selection of an objectdisplayed for the selectable object field, and (b) a sign-in mechanismauthenticates and signs the first user into the IETM based at least inpart on a first user credential, the dataset, the selection of the unitdisplayed, and the selection of the object displayed; provide a secondsign-in window for display, the second sign-in window comprising anelectronic form via a second IETM viewer executing on a second usercomputing entity being used by a second user signed into the IETM,wherein (a) the second user provides (i) input of a selection of adataset corresponding to the technical documentation for one of the oneor more items, (ii) input of a selection of a unit displayed for theselectable unit field, and (iii) input of a selection of an objectdisplayed for the selectable object field, and (b) a sign-in mechanismauthenticates and signs the second user into the IETM based at least inpart on a second user credential, the dataset, the selection of the unitdisplayed, and the selection of the object displayed; provide an ITEMwindow for display via the first IETM viewer executing on the first usercomputing entity, the ITEM window displaying at least one of the textualinformation or a graphical image; receive input of a selection of anannotation selection mechanism provided via the ITEM window; andresponsive to receiving the input of the selection of the annotationselection mechanism provided via the IETM window, provide an annotationwindow, for annotating at least one of the textual information or thegraphical image, wherein the annotation window comprises at least one ofan attach file mechanism, an image capture mechanism, a share mechanism,or a change request mechanism; receive input of a selection of thechange form mechanism, wherein the selection of the change formmechanism is performed by the first user via the first IETM viewer; andresponsive to receiving the input of the selection of the change formmechanism: provide an electronic change form comprising a plurality offields for display via the first IETM viewer; pre-populate at least onefield of the plurality of fields on the electronic change form based atleast in part on information provided in the annotation; and submit arequest for change to at least one of the textual information or thegraphical image based at least in part on information provided on thechange form.
 12. The non-transitory computer storage medium of claim 11,wherein the annotation window further comprises a freeform fieldconfigured to allow the user to enter a comment recorded for theannotation.
 13. The non-transitory computer storage medium of claim 11,wherein the instructions are configured to cause the one or moreprocessors to at least perform operations configured to record a dateand a time when the annotation was generated along with the annotation.14. The non-transitory computer storage medium of claim 11, whereinresponsive to receiving the input of the selection of the change formmechanism, the instructions are configured to cause the one or moreprocessors to at least perform operations configured to attach at leastone of the file and the image to the request for change.
 15. Thenon-transitory computer storage medium of claim 11, wherein theinstructions are configured to cause the one or more processors to atleast perform operations configured to: receive input of a selection ofa mechanism to view a list of annotations, wherein the selection of themechanism to view the list of annotation is performed by the first uservia the first IETM viewer; and responsive to receiving the selection ofthe mechanism to view the list of annotations: generate a list ofannotations window comprising the list of annotations comprising theannotation for at least one of the textual information or the graphicalimage; and provide the list of annotations window for display via thefirst IETM viewer, wherein the list of annotations comprises annotationscreated by the first user the list of annotations window is configuredto allow the user to select an annotation found in the list ofannotations to view.